Hi,
I read in the documentation of wxSplitterWindow :
wxSplitterWindow::SplitHorizontally (wxWindow* window1, wxWindow* window2,
int sashPosition = 0)
<snip>
sashPosition
The initial position of the sash. If this value is positive, it specifies
the size of the upper pane. If it is negative, it is absolute value gives
the size of the lower pane. Finally, specify 0 (default) to choose the
default position (half of the total window height).
For me even with negative sashPosition always the _top_ window keeps it's
size.
I'm using wxPython 2.4 on Windows(2000).
Is this a known bug or is it even fixed in the very latest release ?
Hi,
I read in the documentation of wxSplitterWindow :
wxSplitterWindow::SplitHorizontally (wxWindow* window1, wxWindow* window2,
int sashPosition = 0)
<snip>
sashPosition
The initial position of the sash. If this value is positive, it specifies
the size of the upper pane. If it is negative, it is absolute value gives
the size of the lower pane. Finally, specify 0 (default) to choose the
default position (half of the total window height).
For me even with negative sashPosition always the _top_ window keeps it's
size.
It's only used for the size of the lower pane for the initial sizing. I agree that it would be nice to have it carry over for resizes as well, but nobody has done it yet as far as I know. It could also be done in your code too in an EVT_SIZE handler that sets the position of the sash.
ยทยทยท
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!