It is very easy to draw and/or generate a *multi-point vector path* on a
stack
and then *animate* a control to move along it like this:
*move* the *btn* "button" to the points of the *graphic* "wiggle" in 30 secs
but is looks, frankly, bl**dy silly except in the most trivial of instances.
So I had the "daft" idea of using either:
a button with a rapidly changing *icon*,
or
a graphic object with a rapidly changing *backPattern*
to give the illusion of *animation* in a way that is, at least, a bit
less silly.
HOWEVER . . .
It seems that commands such as
move the btn "button" to the points of the graphic "wiggle" in 30 secs
are very difficult to*interrupt* with*animation sequences* such as this:
set the icon of btn "button" to the id of img "prawn1"
wait 3 ticks
set the icon of btn "button" to the id of img "prawn2"
wait 3 ticks
set the icon of btn "button" to the id of img "prawn3"
wait 3 ticks
set the icon of btn "button" to the id of img "prawn4"
wait 3 ticks
AND, in an*ideal situation* that sort of sequence of commands should NOT
interrupt
the move command but run *concurrently*.
Richmond.
_______________________________________________
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
