OK, OK . . .
So, if I have a series of images being flipped-through inside a graphic
'frame' and DON'T
have any *wait* statements the thing happens so quickly I cannot see the
animation at all: so, to get
60 frames a second, presumably, one has to have a *wait 1 tick*
statement between each frame change?
That is easy to do with frame animations . . .
Bit is it re scrolling?
On 3.12.19 15:03, Colin Holgate via use-livecode wrote:
For Mickey Mouse, he would have been updated 12 times per second, and almost
all cartoons you’ve ever watched were animated at 12 frames per second. The
film was projected at 24 frames per second, and all normal movies you’ve seen
in a cinema were also at 24 frame per second. PAL TV is 25 frames per second,
and NTSC is 30 frame per second. So, those frame rates are clearly acceptable.
But, they are animations and not scrolling. With scrolling, updates of 12 per
second are very noticeable, and even 30 frame per second can be seen as not
smooth. Open a browser on a mobile device and scroll the page. It’s smoothly
updating at 60 frame per second. I think that’s what people are asking for, not
animated GIFs.
_______________________________________________
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
