Another examples of the screen refresh problem on the Mac?
jhurley0305 at sbcglobal.net
Wed Oct 12 09:10:04 EDT 2011
Thank you for this Bernd. It is going to take me a while to digest these new graphic features in 5.0. I confess I am unaware of the interaction between RR code and the display on the screen. That's probably important. :-)
Like you, I don't see much improvement of 5.0 over 4.6 in animation. The effect of lowering the syncRate, not so much the rate as the time between syncs (?), is significant, but then that was something available to us in 4.6--except that I didn't know it. The nomenclature suggests that it is the frequency, when it appears to be the period. And, as we all learned in physics, one is the reciprocal of the other.
I would like to see a little help from RR on these new features--by way of a demonstration stack perhaps.
> Message: 10
> Date: Tue, 11 Oct 2011 12:40:46 -0700 (PDT)
> From: BNig <niggemann at uni-wh.de>
> To: use-revolution at lists.runrev.com
> Subject: Re: Another examples of the screen refresh problem on the
> Message-ID: <1318362046019-3895717.post at n4.nabble.com>
> Content-Type: text/plain; charset=us-ascii
> to anyone who is interested in the stack moving two graphics and different
> settings of syncrate, a handler that calls itself and does a lock screen
> wait for syncrate milliseconds and unlock screen
> and the Livecode 5.0 options of compositortype/tile/cache and layer mode and
> wants to test all the possible variations by optionMenus checkboxes etc here
> is the stack to test (basically the one I sent to Jim Hurley plus the
> livecode 5 options)
> I still don't seem to get the Livecode 5.0 graphic options. At least I only
> see minor improvements with moving two graphics along a path of 180 points.
> The largest effect on smoothness comes from reducing the syncrate. And I
> agree with Colin that the dictionary has it the wrong way around: the lower
> the syncrate the smoother the movement and the higher the processor load.
> A little to the smoothness is added by calling a handler during movement
> that lock/pauses/unlocks the screen. Graphic effects do not seem to be of
> much difference.
> I am still not shure about the optimal settings.
> Kind regards
More information about the Use-livecode