Use idle as scott said? Or, if you don't need it to be super responsive. IE you're using visual cues as andre suggested, then polling every 100 or 150 milliseconds might suffice. Idle is probably easiest. Was wondering about the external, seems that since this is related to os/arch even an external would just have to sit there polling also. (though it could do it in it's own little area and only speak up when a key changes state) So an external would probably be the best option except for that whole "having to write it" thing.
On Sun, Dec 2, 2012 at 8:42 AM, Richmond <richmondmathew...@gmail.com>wrote: > On 12/02/2012 05:30 PM, Mike Bonner wrote: > >> Late to this discussion but.. Polling (or maybe an external?) is the only >> real solution for this problem right? >> >> >> >> > Polling the key downs is possible, but will slow down > a program considerably. > > ______________________________**_________________ > 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<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
