I've had similar problems using the snapshot command, where the engine seems to get behind. My latest problem was my own fault, though where I had locked the screen and it couldn't update. What fooled me was that when I put in a breakpoint, the breakpoint unlocked the screen and it looked as I expected. Finally, after getting a night's sleep, I tried an unlock screen command and it all worked as desired.
I don't know if this would be considered a bug, but it is certainly a way the debugger can give a confusing result. Best, Bill William Prothero http://es.earthednet.org > On Jun 7, 2014, at 9:36 PM, As_Simon <[email protected]> wrote: > > larry wrote >> If I debug and step through it, it always seems to work. > > This, it seems, always points toward the engine is not keeping up. > A "wait 1 millisec" before "if the label of button thisButton = "?" then" > tends to clear it up. (maybe somewhere else but in that area) > > Simon > > > > -- > View this message in context: > http://runtime-revolution.278305.n4.nabble.com/please-help-tp4680326p4680333.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 _______________________________________________ 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
