Actually, the workaround I was thinking of trapped mouseUp in the card or stack handler, then used the command focus on nothing. This will force the loss of focus by the field thereby forcing a closeField to be sent to the field that lost the focus.
This way you can use closeField in fields, and still trap for those mouseups. Just be sure to pass mouseUp in all of your button handlers and you are good to go! Bob On Oct 25, 2011, at 4:24 PM, James Hurley wrote: > Thanks all for the info about the effect of closeField. > > I have assumed that it was called only when a field is closed. > > As you point out it is also called when the field loses focus. > > It appears that that will happen when one clicks in another field or on the > card, BUT not when one immediately clicks on another button. > > That would be a problem in my application. The user could change the field > and then immediately click a button, a button that will not see the effect of > the chance in the field. > > My tortured script at least sends the "change" message as soon as the mouse > leave the field. > > Jim > _______________________________________________ > 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 _______________________________________________ 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
