Brahmanathaswami wrote:
I think what is happening is: even though Auto tab is off, if you have
a field exposed on a card and go to that card the cursor "jumps" into
the field... not matter what mode the stack is in...
Should I report this?
I'm sure they're aware of it. The bigger question is: do we want to
change it?
As far back as I can remember we've had that behavior, presumably
implemented as a convenience for developers since in most cases an
editable field is for, well, editing, so when the window gets focus the
first editable field gets focus.
Sounds good in theory, but more than a few of us have had occasion to
need to work around it, sometimes more easily done than others (the
engine can be very insistent when it want to be).
So we have to ask ourselves: do we want to have to explicitly script all
field focus when a stack window gets focus? Will developers find that
annoying to have to write, or feel liberated no longer having to write
workaround when the current behavior isn't what they want?
Personally I think there are bigger fish to fry (man, it would so cool
if I could just copy and paste text on Linux, or have an option control
with a label that could be read, or a text baseline on ostensibly
"standard" buttons that's actually in a standard position), but maybe
this is important to some...
--
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
