On 16 May 2021, at 01:48, Dave Jordan wrote:
> 
> perish the thought! The part of my event processing that needs to be as responsive as possible deals with individual keystrokes.
> If i have to start strcmping this input its going to ruin my day.

Hmm - do you actually *know* this is slow? When I read this, if I’m honest, my first thought was “premature optimization”...

My experience suggest strongly that the simple way might well be more than fast enough, on any recent computer.
I’d strongly suggest trying the easy thing first, and only doing the complicated “manual” handling if it actually proves necessary (which I suspect it will not, TBH.)


> OTOH, if non-EN-US keyboards prevent FLTK from using event_key() then I guess i'll be forced to look at event_text().

Indeed... amongst other things.

> What about output, you may ask.
> If you know Scrabble and its ilk (which is what my app is all about), you know that there are typically wildcard tiles that are blank.
> But blank doesn't cut it for the UI, so I've already built the capability of mapping from any keystroke to any glyph that the user can compose.
> 

My experience of Scrabble suggests it is not exactly a fast-paced game where serious optimisations are required to support effective gameplay...




-- 
You received this message because you are subscribed to the Google Groups "fltk.general" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/71D95DFF-A157-455D-B356-66CBE6C26567%40gmail.com.