User forums > General (but related to Code::Blocks)

wxWidgets official release 2.6.3

<< < (3/4) > >>

MortenMacFly:
I may have made progress concerning this issue. If you compare the settings of two C::B compilations - one using wxWidgets 2.6.2 and the other using wxWidgets 2.6.3-RC2 then C::B saves the settings differently as following:
This is how it's done with wxWidgets 2.6.2:

--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocksConfig version="1">
<app>
<main_frame>
<layout>
<view1>
<DATA>
<str>layout1|name=MainToolbar;bestw=308;besth=23|name=CompilerToolbar;pos=319;bestw=342;besth=23|name=DebuggerToolbar;pos=672;bestw=215;besth=23|</str>
</DATA>
</view1>
</layout>
</main_frame>
</app>
</CodeBlocksConfig>

--- End code ---
...and this how it's done with wxWidgets 2.6.3-RC2:

--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocksConfig version="1">
<app>
<main_frame>
<layout>
<view1>
<DATA>
<str>layout1|name=MainToolbar;bestw=792;besth=26|name=CompilerToolbar;pos=803;bestw=792;besth=26|name=DebuggerToolbar;pos=1606;bestw=792;besth=26</str>
</DATA>
</view1>
</layout>
</main_frame>
</app>
</CodeBlocksConfig>

--- End code ---
As you can see the issue is that bestw is computed differently (wrong in the case of wxWidgets 2.6.3-RC2). This results in the toolbar being too wide. Now we have to dig into the source code of C::B first to see where this is calculated and whether there maybe a bug inside C::B...
I don't have the time to do this now, but I'll have a look into it tomorrow.
With regards, Morten.

MortenMacFly:

--- Quote from: MortenMacFly on March 20, 2006, 07:32:57 pm ---I may have made progress concerning this issue. [...]

--- End quote ---
BTW: The bestw value is computed in manager.cpp which is part of wxAUI - So I agree with Takeshi Miya who in another topic (I forgot where) pointed to wxAUI, too.
With regards, Morten.
Edit: By now I realised that bestw is strangely always computed to the value 792. But why is beyond my knowledge (so far...)

thomas:
By principle, I tend to always take the opposite of what Takeshi says for granted.

Look into main.cpp, lines 517 and 528. We are setting the main frame's width to 800 pixels and are using the clientsize (as it happens, 592 pixels ;) ) to initialise the "best" size a couple of lines later. wxAUI is entirely innocent.

MortenMacFly:

--- Quote from: thomas on March 20, 2006, 09:39:42 pm ---Look into main.cpp, lines 517 and 528. [...]

--- End quote ---
Alright, point taken.
By now I've also compiled the wxAUI samples which work fine with wxWidgets 2.6.3-RC(x), indeed.
You said the client size is 592 - so where are the 200 pixels difference to 792 are coming from? And where is the client size being actually set? Sorry, I didn't really get it. :oops:
With regards, Morten.

thomas:

--- Quote ---You said the client size is 592 - so where are the 200 pixels difference to 792 are coming from?
--- End quote ---
They come from me being tired... :)  They're 792 pixels, of course.

Navigation

[0] Message Index

[#] Next page

[*] Previous page