A variation of this script shows that lockmoves is getting set to false before
the first move command. Given:
on mouseUp
put 200 into x
put 200 into y
put 2 into dx
put 1 into dy
repeat 100 times
put x,y & cr after tPoints
add dx to x
end repeat
put 200 into x
put 200 into y
repeat 200
put x,y & cr after tNewPoints
add dy to y
end repeat
put empty into mmsg
lock moves
put the lockmoves into mmsg
move button "two" to tPoints without waiting
put comma and the lockmoves after mmsg
move button "one" to tNewPoints without waiting
put comma and the lockmoves after mmsg
unlock moves
put comma and the lockmoves after mmsg
put mmsg
end mouseUp
I get truefalsefalsefalse in the message box. Odd though that there are no
commas?? But I digress. It is obvious that the first move command is setting
lockMoves to false. This has to be a bug.
Bob
On Oct 10, 2011, at 4:04 PM, James Hurley wrote:
> Ken,
>
> Thanks for your careful test. This is driving me nuts and I can't find a
> work-around.
>
> I think the problem is RR not doing a screen refresh after each of the
> MULTIPLE steps. (I have always, in OS 10) had to do a refresh after EACH step.
>
> Would you please try this for me:
_______________________________________________
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
