Another examples of the screen refresh problem on the Mac?

[James Hurley]

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:

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

   lock moves
   move button "one" to tNewPoints without waiting
   move button "two" to tPoints without waiting
   unlock moves

end mouseUp

When I tried your script I  got what you got: Smooth motion. But with the script above, eliminating possible problems with the graphics, I get herky-jerky motion with the second move. I suspect it is due to the multiple steps in the move.

Running RR 4.6.3 and Mac OS 10.6.8

Thanks again,

Jim


> Jim, I'm not seeing that on my Mac (I'm running Lion if that makes any difference, and LC 4.6.4). Does either your oval or rectangle have graphic effects applied to it? Perhaps something like that is slowing down redraw…
> 
> Just to compare, here's what I did:
> 
> 1) Created a new stack, made the window like 1024x768 (approximately.
> 2) Created an oval graphic in the upper-left corner of the window
> 3) Create a rectangle graphic just underneath it
> 4) Dragged a button to the lower-right corner of the window
> 5) Dragged a button to the lower-left corner of the window and edited its script to read:
> 
> on mouseUp
>    lock moves
>    move grc 1 to the loc of btn 1 without waiting
>    move grc 2 to the loc of btn 1 without waiting
>    unlock moves
> end mouseUp
> 
> Switched to browse, and then executed it - the movements were smooth and no jerkiness. Since I don't know what values you have in tPoints or tNewPoints, maybe you can try what I did and see if you get the same result? If so, then it might be the number of points or something else related to properties of the graphics themselves.
> 
> Ken Ray
> Sons of Thunder Software, Inc.
> Email: 
> kray at sonsothunder.com
> 
> Web Site: 
> http://www.sonsothunder.com/