For those interested, I have reported the bug below and (separately) the fact that 'openField' can be triggered in surprising circumstances (the subject of my original post under this heading) - which people here have reported as being an ancient quirk of LiveCode, Runtime Revolution and maybe even MetaCard. Interestingly, RunRev have now accepted BOTH these as bugs (13274 and 13271).
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
