Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
wxAUI evaluation
takeshimiya:
Just for the record, the next version (1.0) will address:
* Add "chevron" button support for toolbars that become partially hidden off screen
* Add hide/show control for docked panes
* Fix minimum/maximum size issues
* Optimize frame docking hint locations and mouse drop locations
* Streamline the "feel" of frame and toolbar dragging
* Fix various drawing glitches and toolbar instability
280Z28:
--- Quote from: mandrav on December 31, 2005, 09:31:40 am ---
--- Quote from: 280Z28 on December 31, 2005, 09:16:01 am ---Do you think we will end up switching to wxAUI in the trunk?
--- End quote ---
Quite possibly, yes.
--- Quote from: 280Z28 on December 31, 2005, 09:16:01 am ---I've already fixed some bugs in my local copy and implemented active/inactive windows.
--- End quote ---
Do you care to explain?
--- End quote ---
If you click the close button with your left mouse button, then move off the button before letting the mouse button up, the close button will not be highlighted but the pane still closes. I fixed that.
I made the default caption colors for inactive panes wxSYS_COLOUR_INACTIVECAPTION and for the active pane wxSYS_COLOUR_ACTIVECAPTION. Nothing too special about that part.
280Z28:
--- Quote from: Takeshi Miya on December 31, 2005, 09:34:17 am ---Just for the record, the next version (1.0) will address:
* Add "chevron" button support for toolbars that become partially hidden off screen
* Add hide/show control for docked panes
* Fix minimum/maximum size issues
* Optimize frame docking hint locations and mouse drop locations
* Streamline the "feel" of frame and toolbar dragging
* Fix various drawing glitches and toolbar instability
--- End quote ---
I really hope 1.0 comes along quickly. It's kinda hard to tell how that project is developing. The source for 0.9 is available, but the forum is empty and there is no svn access (that I saw).
I'll post over there and see about some things I have questions about. I expect C::B to keep using their code, but if for some reason we need to change it in the future it wouldn't be too hard.
I'm going to switch back to trunk for now. I really liked what I saw in wxAUI, and the "feel" was excellent (pane positioning and movable toolbars especially). I hope to see it merged soon. 8)
mandrav:
--- Quote from: Ceniza on December 31, 2005, 01:13:52 am ---Ok, I built it and looks promising, but it isn't saving or loading any layout (you said you implemented that, so where did you hid it?).
--- End quote ---
Lol, I 've hidden it in "View->Layouts" :)
(although I noticed a little glitch and I 'll fix it soon)
--- Quote from: Ceniza on December 31, 2005, 01:13:52 am ---The second problem is the toolbars are a bit bigger than the space assigned for them when icons are 32x32, and smaller when 16x16. In the first case it's painting a few extra pixels, in the second case it isn't painting all pixels (the ones at the bottom), and, also for 16x16, the space for the toolbar is larger than needed.
I suppose those are wxAUI problems, right?
--- End quote ---
This problem already appears with wxDockit. It is probably a C::B issue, specifically because we 're loading the toolbars from XRC. Somehow it seems the bitmap size is not correct. When using the 16x16 bitmaps, if you edit the toolbars' XRCs <bitmapsize> and make it 16,14 instead of 16,16 everything is ok then. Except that some icons are clipped...
takeshimiya:
Reporting in.
Noticed all the problems with the toolbars. Can't we just not load them from XRC?
I'd suggest adding settings for: Allow Floating, Transparent Hint, Transparent Hint Fade-in, and Transparent Drag, somewhere in Settings->Environment.
I would also like to have the ability to set-up Pane Border Size, Gripper Color, etc but a dialog (GUI) for those others is rather worthless.
As I don't like having any hard-coded settings in C::B, here's when my idea comes:
What about those settings (among a lot others) which doesn't deserve a GUI, being setteable from an about:config like in Firefox?
Which of course can be implemented as a tree/listbox in a dialog that haves all the settings of the xml default.conf.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version