altkey() down, up & halfway down

[Mike Bonner]

Yeah, too true.  And if others are like me, having to wait for things to
catch up is really annoying!

Well, this is only osx (objective c) and I'm clueless about it, but the
example on this page might give someone who isn't a clueless c nub like me
a chance to build an external to catch key presses.
http://stackoverflow.com/questions/12113795/is-there-a-keyup-method-for-flagschanged



On Sun, Dec 2, 2012 at 9:39 AM, Richmond <richmondmathewson at gmail.com>wrote:

> On 12/02/2012 05:58 PM, Mike Bonner wrote:
>
>> Use idle as scott said? Or, if you don't need it to be super responsive.
>>
>
> My Devawriter does have to be 'super responsive' as it is, ultimately, a
> glorified typewriter,
> and as such should, in an ideal situation, work not much more slowly than
> the speed one might enter
> text into a text editor. For the sake of argument, even though I type with
> only 2 fingers and have to
> keep looking at the keyboard, I still manage to knock out about 50 words a
> minute!
>
> Obviously there isn't all that much 'idle' when someone is bashing away on
> the keyboard.
>
>
>  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.
>>
>>
>>
>
> ______________________________**_________________
> use-livecode mailing list
> use-livecode at 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>
>