OpenField mystery

Peter M. Brigham pmbrig at gmail.com
Sat Aug 23 17:11:37 EDT 2014


On Aug 23, 2014, at 4:02 PM, Graham Samuel wrote:

> My user is allowed to write stuff into a succession of fields, and then click on a button to get something done. The 'something' depends on whether any of the fields have been modified or not. It is quite possible for him (her) not to close the last revised field, but simply to go straight to clicking the button. This means that I can't rely on a 'closeField' message being generated even when a field is modified! Because of this anomaly I tried to detect field revision by looking at 'openField' messages instead, and just got into another fine mess. Maybe a correctly placed 'focus on nothing' will do it (should close the field where the cursor was last showing) - I will look into it.

put 
   select empty
as the first line in your mouseup handler.

-- Peter

Peter M. Brigham
pmbrig at gmail.com
http://home.comcast.net/~pmbrig





More information about the use-livecode mailing list