finding & storing the field that *would* be next on closefield

dunbarx at aol.com dunbarx at aol.com
Sat Oct 19 17:48:11 EDT 2013


Hi.


"would have gone..."


Do you mean the next field in tab order?


I would not ever design a stack where an object containing a running handler might be deleted, just on principle.
Can't you move that process to a handler in the stack, using "send in time" if you want it delayed, as you said?


Craig Newman



-----Original Message-----
From: Dr. Hawkins <dochawk at gmail.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Sat, Oct 19, 2013 3:10 pm
Subject: finding & storing the field that *would* be next on closefield


I need to do some work when closeField happens.  Quite often, this will
mean sending a delayed message to redraw the entire card, as the object
whose handler is running will get deleted.  Storing the field I'm leaving
is not to bad, but is there a clean way to store where I *would* have gone?

This could come from
* tabKey  (not too hard, but annoying to calculate)
* a shift-tabKey
* an arrowKey or modified arrowKey in the first/last line of a field
* a click in another field (hmm, doesn't that make the other field "the
target"?)
* killing the card (OK, fine; don't need to go anywhere)

is there a clean way to find "the fieldImGoingTo of me"? :)
-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

 



More information about the Use-livecode mailing list