Also I discovered a bit of a flaw in my code. If I click on a field that is a
part of a group then I will likely throw an error, because you cannot set a
fields layer to something higher than the layer of the highest layered object
in the group. In other words, you have to change the layer
can see right
away that if I nested groups, I would be in a helluva state. I avoid nesting
groups anyway if I can because it was such a *expletive deleted* working with
groups when I first started.
Didn't Hypercard have a tab order property? That would be a great addition I
think. You could have
Hi all.
Is there some kind of hidden property pertaining to the tab order of objects on
a card? I know about the layer property, but I was hoping there was some kind
of list, so I could set the tab order of fields by entering a repeat loop and
clicking on objects, building a list of them,
The text property holds the tab names, one per line, in left to right
order. One thing I've found useful when chasing down property names is to
set the Preferences option to display property names instead of labels in
the Inspector dialogs.
On Tue, Dec 6, 2011 at 10:29 AM, Bob Sneidar
Belay my last. Pretty simple:
on clickOrder
put the selectedobjects into theObjectList
repeat for each line theObject in theObjectList
set the layer of theObject to top
end repeat
end clickOrder
Hi all.
Is there some kind of hidden property pertaining to the tab order
Sorry Pete I should have explained myself a bit better. I don't meat a tab
panel. I mean the order in which fields get the focus when a user is tabbing
through them. I found a really simple solution. See my prior post.
Bob
On Dec 6, 2011, at 10:45 AM, Pete wrote:
The text property holds the
interspersed with them, or you might want to have other
objects on top of them layerwise (ok - that's not a word, but you get the idea).
I do think a tab-order property is a useful thing to add in addition to the
layer hierarchy.
___
use-livecode mailing list
of objects on the screen - you may want to have
other
non-tabbable objects interspersed with them, or you might want to have other
objects on top of them layerwise (ok - that's not a word, but you get the
idea).
I do think a tab-order property is a useful thing to add in addition to the
layer
