> As Ian wrote already: don't use a window class then, use Fl_Group to derive > your > specific menu class, and add these to your main window.
I'm trying to create an MDI (had to learn what it means...). I created a sort of "Dock" placed in the bottom of my main screen and I use it to open most of the subwindows. I created a website so you can get an idea of what it's all about: http://sites.google.com/site/robotstudyo/ > Without looking at the FLTK code, I can't tell exactly, but I think that > subwindows are not really instantiated if their parent is not shown yet. Maybe > you don't need to show() them twice, but can call redraw() instead on your > main > window to achieve the same (or resize the main window), but that's wild > guessing > now. I tried resizing the window and calling show() once but still 2 calls are required. > I really assume that you won't have any problems if you use Fl_Group to derive > your menus. Using windows to embed in other windows is overkill (and may not > perform as well, since subwindows are *real* windows for the system). Is it > because of their coordinates (starting with 0) why you want to use windows > instead of groups? I'm not really familiar with the differences between Fl_Group and Fl_Window or Fl_Double_Window but I tried to change one of my classes to inherit from Fl_Group but that crashed the program. Here's some more info: Unhandled exception in Code.exe: 0x000000C5: Access Violation This happens when I call "hide()" on the Group or when I get to show() MainWin. Here's the Dissasembly: Fl_Widget::parent: 00442AA0 push ebp 00442AA1 mov ebp,esp 00442AA3 push ecx 00442AA4 mov dword ptr [ebp-4],ecx 00442AA7 mov eax,dword ptr [this] ->00442AAA mov eax,dword ptr [eax+4] 00442AAD mov esp,ebp 00442AAF pop ebp 00442AB0 ret Apparently the problem is when parent() is called. BTW is there a way of getting a notification when I get a reply? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
