On 5/8/13 9:44 PM, Dr. Hawkins wrote:
I know about the textChanged message, but . . .
I have forms with many fields. I have a closeField handler that sets a
flag when something changes, but this only triggers when leaving the field.
My assistant just discovered a bug that I hadn't--
I have fields that have hotkeys in them, one of which closes a group of
fields. If a change is made in one, and the hotkey used to close, that
change doesn't get processed.
I suppose I could set my flag repeatedly whenever a key is pressed, but
this seems processor intensive.
Is there any way inside the keyUp handler to test whether the contents have
changed?
Or is this just a hangover from my 8 bit days with BASIC interpreters?
I'm not sure why trapping every keyUp would be less intensive than using
the built-in textchanged message, which is optimized. Is there a reason
you don't want to use that? It was created for exactly the scenario you
describe. You could remove your closefield handler too if you use it.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.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
