Earlier I wrote: > Related, it occurred to me that it's sometimes annoying to have > to write this handler just to have tabs entered into the text of > a field: > > on tabKey > put tab into the selecction > end tabKey > > So I submitted a request for an allowTabs field property; off by > default, when true it would allow a field to accept tabs the user > types: > <http://quality.runrev.com/show_bug.cgi?id=14836>
In correspondence in that report Mark Waddingham noted that the tabstops property already governs this behavior.
Empty by default, when the tabstops if a field is set to any valid value the Tab key no longer invoked field-to-field navigation, instead inserting the tab character into the field.
Apparently this is even noted in the Dictionary, but it seems I'm not alone in having overlooked it, since the IDE's Inspector uses that script for the field Contents pane.
Needless to say, I've closed that request. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ____________________________________________________________________ ambassa...@fourthworld.com http://www.FourthWorld.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
