> > 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 app's actions on the key-downs and not have too many side > effects in the key-up that I need to trap. Thanks for the suggestions! > If I do see something really weird, I'll try to post gdb back-trace info, > but hopefully I won't need to! -Mike
Would it make sense to try and pair the down and up events, and from there identify "rouge" key-ups to ignore... something like that... SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
