On 2015-08-15 22:53, Martin Koob wrote:
Hi
I found another way to resolve it that works in the sample stack and in
my
application. Reading about the wait command in the dictionary I saw
you can
also use send in time to give LiveCode a chance to process messages.
If I use send in time for both "setState off" and "setState on" then I
can
click the button when it is re-enabled.
Here is the workaround script for the sample button.
on mouseUp
send "setState off" to me in 10 milliseconds
send "setState on" to me in 3 seconds
end mouseUp
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".
Peter
--
Dr Peter Brett <peter.br...@livecode.com>
LiveCode Engine Development Team
_______________________________________________
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
