Perhaps this would need a delay after the pass. For example, wait until the key
is up and then maybe wait a bit more. This would allow all of the events to
come in before they are flushed. Maybe.
(I think my state-variable method is simpler, but simple is in the eye of the
beholder.)
> On Jun 12, 2019, at 4:41 AM, FlexibleLearning.com via use-livecode
> <use-livecode@lists.runrev.com> wrote:
>
> Straw grasping here...
>
> on keyDown
> do something
> send "flush" to me in 0
> pass keyDown
> end keyDown
>
> on flush
> get flushEvents("all")
> end flush
>
> Hugh Senior
>
> On Mon, Jun 10, 2019 at 01:43 Richmond via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Everyyyyyyytttttime I try tooooooooo typppppe sooooommmmmethhhhing
>> myyyy fffffinnnngerrrrrrs ggggget stuuuuuuuck on the keeeeeys tooooo
>> long . . .
>>
>> Especially in LiveCode (!)
>>
>> So?
>>
>> on keyDown
>> do something
>> get me the hell out of this so it doesn't happen more than once end
>> keyDown
>>
>> ?
>>
>> 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
