On 14.05.2012, at 12:04, David Currie wrote: >> On 05/11/12 10:11, Greg Ercolano wrote: >>> On 05/11/12 06:32, Matthias Melcher wrote: >>> If there's bugs/shortcomings with Fl_Text_Display's >>> caret + keynav, we should probably fix it, so that it >>> can be a fully functional replacement for Fl_Multiline_Output. >>> >>> I did notice, as David did, that the caret would sometimes >>> not appear. I found if the window opened when my mouse wasn't in it, >>> the caret wouldn't appear. And moving the mouse INTO the window >>> didn't make it appear. >> >> I've opened STR#2844 for this on David's behalf for this >> to be investigated. >> >> The Fl_Text_XXX widgets seem pretty complex under the hood, >> so I'm leaving it open for someone to investigate who's familiar >> with it. > > Before I discuss caret behavior. > I have a further related issue (it's all bound up in the same widget). > I need to trap all keystrokes so > > Running the program as is You get a keyup for all keys. > Removing all comments and NOW (KP_arrows, arrows, > KP_home,KP_end,home,end,others??) > generate a KEYUP BUT NOT a KEYDOWN(KEYBOARD). I don't understand ?
The Fl_Double_Window does not get keyboard focus by default. You can achieve that by returning 1 for FL_FOCUS and FL_UNFOCUS events. Fl_Input_ and derived widgets and Fl_Text_Display do that for you. _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
