Detect when a field changes

dunbarx at aol.com dunbarx at aol.com
Sun Nov 17 23:31:27 EST 2013


Robert.


You make a point. And it must be accepted that the message is only sent when a human being interacts. At least it is consistent.


Maybe it is the name of the message itself that makes me think it has a quirk, as opposed to a specifically defined functional spec.


Craig Newman



-----Original Message-----
From: Robert Brenstein <rjb at robelko.com>
To: How to use LiveCode <use-livecode at lists.runrev.com>
Sent: Sun, Nov 17, 2013 8:51 pm
Subject: Re: Detect when a field changes


On 16.11.2013 at 23:35 Uhr -0500 dunbarx at aol.com apparently wrote:
>Bill.
>
>I am with you, and any honest LiveCoder ought to be as well. The 
>"textChanged" message should stand on its own feet, if it has any, 
>and do what it advertises.
>

But then, if "textChanged" fires on any change, including scripted 
changes, we need to go through extra hoops to distinguish between 
user-input and script-based changes. The message as it is now means 
Text-Changed-by-User and allow us, for example, verify user input 
(and what if the verification routine programmatically corrects user 
input?). I am not sure that that would really be so useful in the big 
scheme of things.

RObert

_______________________________________________
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