OK, I just checked out again and the warning messages seem to have gone. Yay!
Found a few more bugs to keep you busy...
> Disabling menus doesn't appear to work.
> Tabs don't look right for some reason (see IDE options). I think this is because of the way GTK handles tabs which is more automated than the MaxGUI API of hiding and showing your own panels. I think you tackled this problem by resizing the effective tab area to a thin strip that just contains the tabs, but Skid got around this in FLTK by creating a single client to which all tab children are added to, and then calling the FLTK setParent() method, reassigning the panel to the currently selected tab-widget. This seems to work quite well and this way, you get the full tabber widget drawn.
> Child windows (windows with a group specified - the undocumented WINDOW_CHILD flag is obsolete now and is ignored by most of the MaxGUI drivers) aren't staying in front of parent windows.
> The only way to keep the context menu open in the TextArea is to hold down the right mouse button. Clicking the right mouse button causes it to show but then hide again in quick succession.
> LookUpGuiFont() - I think we're gonna have to get GTK to return more suitable fonts than the hardcoded presets, as the navbar and output fonts chosen just doesn't look write with the rest of the GTK themed controls. I'll have a mooch around the GTK docs tomorrow if I get a chance.
And finally, a minor point, but on my PC the GTK IDE seems to take quite a long time to start up, getting stuck at a particular point on the splash-screen compared with the FLTK IDE. I'm guessing its the population of the treeview, but I'll have a deeper look into this tomorrow.
Found a few more bugs to keep you busy...
> Disabling menus doesn't appear to work.
> Tabs don't look right for some reason (see IDE options). I think this is because of the way GTK handles tabs which is more automated than the MaxGUI API of hiding and showing your own panels. I think you tackled this problem by resizing the effective tab area to a thin strip that just contains the tabs, but Skid got around this in FLTK by creating a single client to which all tab children are added to, and then calling the FLTK setParent() method, reassigning the panel to the currently selected tab-widget. This seems to work quite well and this way, you get the full tabber widget drawn.
> Child windows (windows with a group specified - the undocumented WINDOW_CHILD flag is obsolete now and is ignored by most of the MaxGUI drivers) aren't staying in front of parent windows.
> The only way to keep the context menu open in the TextArea is to hold down the right mouse button. Clicking the right mouse button causes it to show but then hide again in quick succession.
> LookUpGuiFont() - I think we're gonna have to get GTK to return more suitable fonts than the hardcoded presets, as the navbar and output fonts chosen just doesn't look write with the rest of the GTK themed controls. I'll have a mooch around the GTK docs tomorrow if I get a chance.
And finally, a minor point, but on my PC the GTK IDE seems to take quite a long time to start up, getting stuck at a particular point on the splash-screen compared with the FLTK IDE. I'm guessing its the population of the treeview, but I'll have a deeper look into this tomorrow.