On 11 Dec 2009, at 10:29, manolo gouy wrote: > > Let's do a recap of where we are now. > I upload file recap.zip containing all modified source code (and .h) > to avoid svn diff problems, and will follow Greg's advice thereafter.
Yup - files in the zip seem to be good, thanks. One thing, IIRC there was a patch to Fl_Preferences too - should we be looking at that one also? > Solved issues: > - non-antialiased fonts under 10.4 Confirmed: seems good now on 10.4.11 / PPC > - Sudoku crash Seems OK. The Sys_Menu_Bar does not have any shortcuts displayed - would I expect it to? The menubar demo does have shortcuts displayed, but they seem to have the "saucepan" symbol - the alt key modifier. I think I expected them to have the "cloverleaf" symbol - the "cmd" key modifier? Well, maybe not, I don't know. Oh, that's an odd thing - I just noticed that the "saucepan" is upside down... it is the opposite way up from what I have on my keyboard. Checking... Yes, it appears to be the "normal" way up on other apps. Weird. I wonder how we managed that... > - vanishing "About myprog" window Yes, seems to be better now. > New API proposal: > - fl_mac_set_about(const Fl_Menu_Item *item) > to connect an FLTK menu item to the "About myprog" application menu > item Sounds like a good idea to me. > Extending Fl_Sys_Menu_Bar towards more complete FLTK behavior: > I have added these two member functions (that's new): > int add(const char* label, int shortcut, Fl_Callback*, void > *user_data=0, > int flags=0); > void remove(int n); > so system menus can now also be modified programmatically. This > is done in a very brutal way (delete the whole menu bar and recreate > it fully after any add or remove) but it requires very, very little > code (so hopefully no bug). Sounds very good - have not tested this functionality yet. > Pending issues: > - white footprint behind Fl_Native_file_Chooser wwindow in Ian's app I have been testing this with a debug build (both fltk and my own code compiled with -g) and the behaviour is slightly different now: - If I open a FNFC (Fl_Native_File_Chooser) then close it without interacting with it in any other way, then I sometimes get the "white rectangle" sometimes not. - Whether I get the "white rectangle" or not, the app becomes unresponsive. - All the menu options in the Sys_Menu_Bar are greyed out. - If I do interact with the FNFC (e.g. try to type in a file name) I get a segfault like this: 2009-12-11 18:02:48.791 dnd-edit[8498] *** -[NSCarbonWindow getFl_Window]: selector not recognized [self = 0x13be280] 2009-12-11 18:02:48.791 dnd-edit[8498] An uncaught exception was raised 2009-12-11 18:02:48.792 dnd-edit[8498] *** -[NSCarbonWindow getFl_Window]: selector not recognized [self = 0x13be280] 2009-12-11 18:02:48.792 dnd-edit[8498] *** Uncaught exception: <NSInvalidArgumentException> *** -[NSCarbonWindow getFl_Window]: selector not recognized [self = 0x13be280] Program received signal SIGTRAP, Trace/breakpoint trap. 0x92c11490 in _NSRaiseError () (gdb) bt #0 0x92c11490 in _NSRaiseError () #1 0x92c111cc in +[NSException raise:format:] () #2 0x92bea290 in -[NSObject(NSForwardInvocation) forward::] () #3 0x90a460b0 in _objc_msgForward () #4 0x0003c1f0 in carbonTextHandler (nextHandler=0xbfffde90, event=0x13b3100, unused=0x0) at Fl_cocoa.mm:980 #5 0x932bb934 in DispatchEventToHandlers () #6 0x932bb08c in SendEventToEventTargetInternal () #7 0x932c1e90 in SendEventToEventTarget () #8 0x933d0120 in SendTSMEvent () #9 0x933cf870 in SendUnicodeTextAEToUnicodeDoc () #10 0x933cf29c in utDeliverTSMEvent () #11 0x933cee80 in TSMKeyEvent () #12 0x93385b34 in TSMProcessRawKeyEvent () #13 0x933855fc in HandleCompatibilityKeyEvent () #14 0x932b86a4 in HIApplication::EventHandler () #15 0x932bb934 in DispatchEventToHandlers () #16 0x932bb08c in SendEventToEventTargetInternal () #17 0x932baf08 in SendEventToEventTargetWithOptions () #18 0x933852a4 in HandleKeyboardEvent () #19 0x932c220c in ToolboxEventDispatcherHandler () #20 0x932bbb84 in DispatchEventToHandlers () #21 0x932bb08c in SendEventToEventTargetInternal () #22 0x932c1e90 in SendEventToEventTarget () #23 0x93302c04 in ToolboxEventDispatcher () #24 0x933a1a10 in TryEventDispatcher () #25 0x933a1668 in GetOrPeekEvent () #26 0x933a14c0 in GetNextEventMatchingMask () #27 0x933a1244 in WNEInternal () #28 0x933a1198 in WaitNextEvent () #29 0x93211b3c in TBrowseDialog::EventLoop () #30 0x93208af4 in TBrowseDialog::StartDialog () #31 0x931f6a14 in __NavDialog::Run () #32 0x931f6948 in NavDialogRun () #33 0x00031ec8 in Fl_Native_File_Chooser::post (this=0x1839e00) at ./ native_file_chooser/src/Fl_Native_File_Chooser_MAC.cxx:595 #34 0x000321d8 in Fl_Native_File_Chooser::show (this=0x1839e00) at ./ native_file_chooser/src/Fl_Native_File_Chooser_MAC.cxx:511 #35 0x00029d7c in pdf_render () at page-preview.cxx:77 (etc...) > - drag crash in Ian's app Fixed with the additional check as recounted in other posts. > - nonfunctional keyboard accelerators in Ian's app This is a bit of an odd one - I'm having trouble pinning down what is going on. I think part of the problem is that a lot of the keyboard accelerators are actually set via the menu shortcuts mechanism and that seems to be not working fully yet - none of my menu shortcuts seem to be filled in. In addition, a lot of the keyboard accelerators are using modifier keys, and these don't seem to be mapping in correctly. So things that are <shift><key> seem to work OK, but ones that are <ctrl><key> or <alt><key> seem maybe to not be working. Well, something like that anyway. Investigation continues... _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
