Jacque mentioned the traversalOn property in a previous post.
by jacque » Sat Apr 04, 2015 11:09 am
...turn off the traversalon property...
I think this good comment needs reinforcement regarding fields.
First, arrange fields in the Project Browser to the order desired (so the fields' layers follow sequentially). The tab key will move the focus to the next field.
Second, for any other fields that shouldn't receive focus, set the other fields' traversalOn property to false by clicking off the "Focus with Keyboard" box in the property inspector or use this code:
Code: Select all
set the traversalOn of field "tField" to false
See the "traversalOn" entry in the Dictionary for more information regarding groups and other controls. According to the Dictionary, the stack's "lookAndFeel" property plays a role in this story, too.
According to the Dictionary, the "autoTab" property: specifies whether pressing Return (or Enter) moves to the next field.
I hope that provides some clarity rather than confusion,
Bob