Struggling with message sequence when leaving fields
J. Landman Gay
jacque at hyperactivesw.com
Sat Oct 19 17:52:18 EDT 2013
On 10/19/13 3:41 PM, Dr. Hawkins wrote:
> I'm trying to figure out the sequence of messages when I leave one field
> for another.
> I always assumed that it would first be closeField, then tabKey (or
> whatever caused the change), then the openField for the new field.
> As I'm trying to debug, though, this doesn't seem to be the case.
> I'm not quite certain, but it looks like tabKey begins immediately, with
> closeField put into the message queue--whereupon it starts running while
> I'm still in the debugger for tabKey, causing problems as it deletes the
> running script . . .
> Do I have this sequence right?
Key events happen before field events (they'd have to, when you think
about it.) So right, tabkey would occur before closefield.
You can always see the order for yourself by opening the Message Watcher
from the Development menu and watching what happens as you use your
stack. You might want to suppress all the IDE and mouse messages to
prevent the list from filling up with stuff you don't care about.
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
More information about the use-livecode