Peter TB Brett wrote > You can actually also do: > > send "setState off" to me in 0 seconds > > The engine will finish mouseUp, process messages, and then immediately > run "setState off".
Hi Peter Thanks. I have changed to 0 seconds. How messages are processed sent, held and interfere with one another is one area I need to better understand. I am not sure for example when and why I should use lock messages or send in time or wait with messages. I usually only try those when something is not working as expected. Is there a good explanation of this somewhere? I have posted a bug report http://quality.runrev.com/show_bug.cgi?id=15730 Thanks for your help. Martin -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Button-does-not-receive-mouseUP-after-disabling-then-enabling-button-tp4695119p4695164.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
