> This stack dump you gave me shows that when you are in the FNFC, > keyboard events get sent to carbonTextHandler, a function of > Fl_cocoa.mm, and this is bad because FLTK does not > know the FNFC window. > > So, could you, please, try and comment out line > InstallEventHandler(GetEventDispatcherTarget(), > textHandler, 1, textEvents, NULL, 0L); > of file Fl_cocoa.mm (= the last of fl_open_display) and tell me what > happens. > This will preclude character palette input, but I would like > to know what happens then for FNFC.
Will try this later today - did not get a chance yesterday, too much stuff happening in life... Anyway, I was thinking about this (while *not* at a computer and unable to look at the code...) An aspect of my app that might be relevant is that it has multiple windows - the "main" editor window and multiple floating toolbar windows, which are "non-modal". What I am finding is that, after showing and then closing the FNFC the sys_menu_bar for the app is "greyed out" and some (but not all) parts of the app become unresponsive to user interactions. So... I wonder if the presence of the non-modal windows is somehow confusing things, and the code is becoming "disoriented" after showing the FNFC and somehow leaving the code in a state where it thinks a modal window is active and taking some or all of the inputs...? This is distinct from the crash that occurs when I try and type into the FNFC of course, but presumably related... Just some random speculations. -- Ian SELEX Sensors and Airborne Systems Limited 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
