User forums > Nightly builds
The 31 august 2006 build is out.
Vampyre_Dark:
--- Quote from: Phatency on September 01, 2006, 10:32:20 pm ---I can't open symbols browser anymore. It simply does not open. I've tried fresh-installing cb with no luck.
Version 1.0 revision 2936 () gcc 3.4.5 Windows/unicode
WinXP SP2
--- End quote ---
Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.
PDEE:
--- Quote ---Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.
--- End quote ---
I never thought of undocking it :) . I prefer it the old way aswell. Not enough room in the project manager place. Why was it moved?
Phatency:
--- Quote from: Vampyre_Dark on September 01, 2006, 10:56:47 pm ---
--- Quote from: Phatency on September 01, 2006, 10:32:20 pm ---I can't open symbols browser anymore. It simply does not open. I've tried fresh-installing cb with no luck.
Version 1.0 revision 2936 () gcc 3.4.5 Windows/unicode
WinXP SP2
--- End quote ---
Same thign appeared to happen to me too. But it was docked by default as a tab in the project manager. I had to set it to be a free floating window again, and I docked it back the old way.
--- End quote ---
Oh right, that's it, it's already tabbed :D Well, the view-menu certainly should do something when it's selected to avoid these kind of misunderstandings..
Actually, should it even be in the view-menu when it's not a dockable window, but a tab of manager instead?
takeshimiya:
--- Quote from: Phatency on September 01, 2006, 11:21:00 pm ---Actually, should it even be in the view-menu when it's not a dockable window, but a tab of manager instead?
--- End quote ---
The real solution to all of this problem will come from wxAUI and "tear-able tabs". It's on the roadmap already.
If you don't know what "tear-able tabs" are, see it in action for example in wxIFM: http://snakesoft.net/wxifm/demo.zip
EDIT: and wxAUI tabs, http://www.kirix.com/res/aui/auitabs.exe
The thread is here: http://www.kirix.com/community/forums//viewtopic.php?t=169
takeshimiya:
About the wx2.6.2 vs. 2.6.3 toolbar size problems:
--- Quote from: http://wxforum.shadonet.com/viewtopic.php?p=35910#35910 ---The problem is as follows. In wxWidgets 2.6.3, the toolbar's initial client size (when wxDefaultSize) is specified no longer is set to the toolbar's minimum acceptable size. This is slightly different behavior than 2.6.2.
To fix this problem, we added code that sets toolbar initial toolbar sizes to whatever wxToolBar::GetBestSize() returns. Unfortunately, the size that is being returned by the class is too small (vertically). I don't know why.
At any rate, the way to get around this is to do your own wxToolBar::GetBestSize() call, then specify this size on your AddPane call with the BestSize parameter, while at the same time increasing the y parameter by the number of missing pixels.
I hope that wxToolBar::GetBestSize() on win32 can be fixed soon.
Either that, or you can check out the code that is doing the wrong calculation. It's called from wxAUI 0.9.2 on line 1293.
All the best,
Ben
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version