wxSplitterWindows and wxBoxSizers problem

I've just come back to working on a wxPython app that I last touched about a year ago. I've updated my python distribution to 2.3.4 and my wxPython to 2.5.2.8. I'm now slogging through trying to update an app to run with the new versions of everything. I expect this, no complaints.

On thing that seems to be changed is the behavior of my wxSplitterWindows. My main window is a wxSplitterWindow split vertically into a left part and a right part. The left part is also a wxSplitterWindow split horizontally into a top part and main part. The main part is also a wxSplitterWindow split horizontally again into middle part and a bottom part. (I use vertically and horizontally in the preceding in the same sense as the SplitVertically and SplitHorizontally methods). The middle part and the bottom part are both wxPanels, each containing a text label and a tree control, and the layout of each of these panels is controlled by a wxBoxSizer.

The window appearance is changed dramatically for the worse since this program was running with
the versions of python and wxPython from last year. The two top levels of splits of the window work fine, but the split of the main part into the middle part and bottom part is working oddly. After setting
up these windows, print statements to tell me what's afoot say:

Middle Panel Size wx.Size(16, 3)
Middle Panel Pos wx.Point(2, 15)
Bottom Panel Size wx.Size(16, 6)
Bottom Panel Pos wx.Point(2, 2)

What I see is that the entire main part is filled with the middle panel. The middle panel's size in pixels
is visually much bigger than 16 x 3. Is size not in pixels anymore? Bottom panel is not visible at all. There is no hint of it or of the sash that should separate the two panels.

I've looked at the demo code, tried to search the archives, and pondered the help file to try to see what might be different or what I've got wrong, but I didn't find any clues.

Thanks much if anyone has any hints,

Al Christians

Look at the Migration Guide in the docs dir of wxpython. The section on Sizers might help.
If you still have problem after that, try to isolate the problem in a small sample app and post it on the list, someone will take a look and... provide some guidance.

···

On Sat, 09 Oct 2004 22:59:23 -0700, Al Christians <achrist@easystreet.com> wrote:

I've just come back to working on a wxPython app that I last touched about a year ago. I've updated my python distribution to 2.3.4 and my wxPython to 2.5.2.8. I'm now slogging through trying to update an app to run with the new versions of everything. I expect this, no complaints.
[...]
What I see is that the entire main part is filled with the middle panel. The middle panel's size in pixels
is visually much bigger than 16 x 3. Is size not in pixels anymore? Bottom panel is not visible at all. There is no hint of it or of the sash that should separate the two panels. I've looked at the demo code, tried to search the archives, and pondered the help file to try to see what might be different or what I've got wrong, but I didn't find any clues. Thanks much if anyone has any hints,

--
Peter Damoc
Hacker Wannabe