I think the bug is still there: I just created a stack with one button and one field. I can edit the field and then immediately click the button, but the 'closeField' doesn't fire unless I make it do so explicitly, for example with a 'returnInField' handler, or if the whole stack loses focus and then gets it back.
So I plan to report it. Thanks for the confirmation that it is indeed a bug. Graham On 23 Aug 2014, at 23:22, J. Landman Gay <jac...@hyperactivesw.com> wrote: > On 8/23/2014, 3:02 PM, Graham Samuel wrote: >> 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! > > Hm, that's an old bug that I thought got fixed. I remember a while back > noticing that a closefield was sent. If it's broken again, consider putting > in a bug report on it. > > If I remember right, I used to do this in the button: > > if the selectedfield <> "" then send "closefield" to the selectedfield > > but it was a long time ago. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > 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
