Also of interest might be the moveStopped message. > On Jun 26, 2016, at 10:36 AM, J. Landman Gay <jac...@hyperactivesw.com> wrote: > > Use the "without waiting" syntax for the move command, which allows messages > to be generated normally. Then set up a "send in time" structure that checks > the movimgControls, and if the object of interest is in there, change its > icon. > > > On June 26, 2016 10:31:43 AM Richmond <richmondmathew...@gmail.com> wrote: > >> 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*. > > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > > > _______________________________________________ > 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
