Heres my take on it. Moved most of the code to the graphic. Game loops work so much better for this type of thing because you avoid the "arrowkey" repeat problem entirely.
All it does is loop, look at what keys are down, and acts appropriately. Changed the move distance to 5, and increment a counter to pick the next animation frame. Added a start button to start and stop the loop. Great penguin graphics, love the affect! Heres a link to the modified stack. On Sun, Apr 24, 2016 at 1:43 AM, RM <richmondmathew...@gmail.com> wrote: > Of course my next problem is how, when a punter presses the arrowKey to > have it "fire" only once: i.e. then chummy keeps his/her finger on the key > it doesn't continue sending arrowKey signals after the first one. > > 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 > _______________________________________________ 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