> > Hmm. Are you sure it is a key-down event, not a key-up?
>
> I think you are making a good point. The child process aterm is closing
> on the key-down of [enter], but my app is mostly catching key-up events.
> Maybe I can rework it to only work on key-down.Hopefully it will be simple
> to tri
> Hmm. Are you sure it is a key-down event, not a key-up?
I think you are making a good point. The child process aterm is closing on the
key-down of [enter], but my app is mostly catching key-up events. Maybe I can
rework it to only work on key-down.Hopefully it will be simple to trigger my
a
> I've been trying to squash some usability annoyances lately. One issue
> I've had is that I have a global key event handler that should catch the
> enter key (user selects a file in the list window, then presses enter to
> automatically run the preferred associated app for that kind of file).
>
On 09.05.2012, at 21:25, Mike Lockmoore wrote:
> Now, back in my filemanager, a shortcut keypress is passed to the global key
> handler callback function with the enter key event.
Hmm. Are you sure it is a key-down event, not a key-up? Once, 'system' returns,
there is still a pending key-up wh
Hi. I've written a modestly successful file manager for Tiny Core Linux called
Fluff, which is built with FLTK 1.1, since that's what's shipped with Tiny
Core. I have some other FLTK apps out there too. I like FLTK, but I'm stuck
on something.
I've been trying to squash some usability annoya
5 matches
Mail list logo
