Mark Wieder mwieder at
Sat Sep 9 15:06:49 EDT 2006


Saturday, September 9, 2006, 9:40:08 AM, you wrote:

> I think so -- it's just a means you can use (along with openField and
> exitField) to determine what to with fields' contents, for example when you
> change focus across multiple fields.  I don't believe selectionChanged
> handles cases where the cursor simply changes position in different fields
> -- it seems you actually have to select something to trigger
> selectionChanged, whereas open/close/exitField handle basic changes of
> object focus.  Not sure if this is what you're asking.

I think this *is* pretty much what I'm asking. I'm particularly
interested here in the case where the field contents have changed, so
selectionChanged does the trick for me. I'm not really sure why I
would care if the focus changes and the contents haven't changed. And
selectionChanged has the benefit (for me for this case) of not being
triggered if I bring a web browser to the front and then go back to
the app.

-Mark Wieder
 mwieder at

More information about the Use-livecode mailing list