Re: Another example of the screen refresh problem on the Mac?
Ooooh... a train track builder! Bob On Oct 11, 2011, at 11:01 AM, James Hurley wrote: Colin, I was never able to get 9 pool balls to move smoothly. It works but not smoothly. Jim Hurley Colin Holgate wrote: I should update my first Rev stack sometime: http://xfiles.funnygarbage.com/~colinholgate/rev/testtrack.html see if I can get dozens of cars driving around. On Oct 11, 2011, at 12:52 PM, James Hurley wrote: Frustration with animation on the Mac, I guess.) ___ 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 ___ 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
Re: Another example of the screen refresh problem on the Mac?
Colin, Thanks for this. Very informative. I tried, using Brnd's MoveTest utility and the Move command is markedly smoother at a syncRate of 6 over that at 17. I need to do some experimentation to test 5.0. I'm hoping that RR educates us on how best to take advantage of the improvements in animation. Jim Hurley Colin Holgate wrote: I just tried some values, and it appears that the documentation is wrong. The example given of setting it to 12, makes you think that it's 12 frames per second. Saying that 20 is the default and that decreasing the rate will reduce CPU load, but may make things jerky, confirms that the help is talking in terms of frame per second. But, if you try: set the syncrate to 1000 you'll see that there is exactly one update of the Move movement per second. Setting it to 100 give a convincing 10 fps. In other words, the number is the amount of milliseconds between updates, and not the frames per second at all. Setting it to the default of 20 would give you 50 fps, which should be plenty smooth enough for anyone, especially if the company that used that default lives in a country that has PAL TV. I believe that Mac OS and iOS have an effective fixed rate of 60 fps, so if you're using syncrate you may as well use 17 rather than 6. In related news, there is a new iOS specific command, iphoneSetRedrawInterval. With that you can have LiveCode just do updates when iOS does them, which would be a bit like having a syncrate of 16.666, that is in sync with the system redraw. ___ 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
Re: Another example of the screen refresh problem on the Mac?
I see that too, and even setting it to 1 seems better than setting it to 6. It could be that on desktop it still has to wait for the next screen update. The hope for iOS would be that iphoneSetRedrawInterval = 1 will give perfect redraw sync. On Oct 11, 2011, at 10:50 AM, James Hurley wrote: I tried, using Brnd's MoveTest utility and the Move command is markedly smoother at a syncRate of 6 over that at 17. ___ 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
Re: Another example of the screen refresh problem on the Mac?
I should update my first Rev stack sometime: http://xfiles.funnygarbage.com/~colinholgate/rev/testtrack.html see if I can get dozens of cars driving around. On Oct 11, 2011, at 12:52 PM, James Hurley wrote: Frustration with animation on the Mac, I guess.) ___ 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
Re: Another example of the screen refresh problem on the Mac?
Colin, I was never able to get 9 pool balls to move smoothly. It works but not smoothly. Jim Hurley Colin Holgate wrote: I should update my first Rev stack sometime: http://xfiles.funnygarbage.com/~colinholgate/rev/testtrack.html see if I can get dozens of cars driving around. On Oct 11, 2011, at 12:52 PM, James Hurley wrote: Frustration with animation on the Mac, I guess.) ___ 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
Re: Another example of the screen refresh problem on the Mac?
Message: 26 Date: Mon, 10 Oct 2011 22:16:04 -0500 From: J. Landman Gay jac...@hyperactivesw.com To: How to use LiveCode use-livecode@lists.runrev.com Subject: Re: Another examples of the screen refresh problem on the Mac? Message-ID: 4e93b4f4.1010...@hyperactivesw.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 10/10/11 6:04 PM, James Hurley wrote: Ken, Thanks for your careful test. This is driving me nuts and I can't find a work-around. The workaround might be LiveCode 5.0, where animation has been greatly enhanced. That said, I have a script that moves two objects together that also misbehaves in both 4.6.4 and 5.0. What I had to do was make the second object move faster than the first. Both move commands use a time factor, so: move btn btn1 to x,y in 500 milliseconds move btn btn2 to x,y in 100 milliseconds Then they both move together, only at the faster rate. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com Jacque, Thanks. I hadn't upgraded to 5 on the assumption that the changes from 4 were for the mobile apps. Happy to see that animation has not been neglected. A screen refresh is still required in 5.0 if there is a rapid sequence in the change to the location of an object--on the Mac. It is odd however that unlock screen no longer forces a screen refresh on the Mac. However, wait 0 millisec does still work. Something like this works in 4 and 5: if char 1 to 2 of the systemVersion = 10 then wait 0 millisec ...or there is no visible change on the screen--only the final location is seen. And for reasons that I do not understand, setting the syncRate to 6 (Brnd's suggestion) improves the smoothness of the motion. Jim Hurley ___ 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
Re: Another example of the screen refresh problem on the Mac?
Did you read my message yet? On Oct 11, 2011, at 12:29 AM, James Hurley wrote: ...or there is no visible change on the screen--only the final location is seen. And for reasons that I do not understand, setting the syncRate to 6 (Brnd's suggestion) improves the smoothness of the motion. ___ 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
