Detect when a field changes

dunbarx at dunbarx at
Sat Nov 16 23:35:40 EST 2013


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.

Much of what I depend on, and have confidence in, especially such things as the hare-brained string references that we all build in the certainty that the parser will construct (or deconstruct) meaning,  are based on well defined and independent functionality.

It is not enough to simply state that there is a well defined piece missing from that schema, and learn to accept that fact. This is an outrage.

Craig Newman

-----Original Message-----
From: Bill Vlahos <bvlahos at>
To: How to use LiveCode <use-livecode at>
Sent: Sat, Nov 16, 2013 8:12 pm
Subject: Re: Detect when a field changes

Yes I can and have done things like this. But my problem is that it is stupid.

The field knows that something has changed because it has the correct (new) 
information in it.

I find it annoying that I’m the one who has to remember to call a handler when I 
make a change.

Bill Vlahos
InfoWallet ( is about keeping your important life 
information with you, accessible, and secure.
lcTaskList: (
RunRev lcTaskList Forum: (

On Nov 16, 2013, at 4:04 PM, Peter Haworth <pete at> wrote:

> I guess you could also send a textChanged message to the field, or pull the
> textChanged logic into a separate handler and call it from textChanged and
> wherever else you put text into the field.

use-livecode mailing list
use-livecode at
Please visit this url to subscribe, unsubscribe and manage your subscription 


More information about the Use-livecode mailing list