wx.SplitterWindow and sash position setting

wxPython Users
1

There seems to be an inconsistency between the wxSplitterWindow::SplitHorizontally() and wxSplitterWindow::SetSashPosition() on regards to the way the sash position is specified.

For
bool SplitHorizontally(wxWindow* window1, wxWindow* window2, int sashPosition = 0)

the sashPosition argument is sign encoded, where a positive number is used to denote the size of the upper pane, while a negative number is used for the size of the lower pane.

I was expecting the same behavior for the position argument of

void SetSashPosition(int position, const bool redraw = TRUE)

But it does not seems to be the case. For a window height of 800, i must set the sash to 600 to put it at the bottom quarter of the window. The negative number does not work.

Why is it this way?

Thanks

Pierre

2

Pierre Rouleau wrote:

There seems to be an inconsistency between the wxSplitterWindow::SplitHorizontally() and wxSplitterWindow::SetSashPosition() on regards to the way the sash position is specified.

For
bool SplitHorizontally(wxWindow* window1, wxWindow* window2, int sashPosition = 0)

the sashPosition argument is sign encoded, where a positive number is used to denote the size of the upper pane, while a negative number is used for the size of the lower pane.

I was expecting the same behavior for the position argument of

void SetSashPosition(int position, const bool redraw = TRUE)

But it does not seems to be the case. For a window height of 800, i must set the sash to 600 to put it at the bottom quarter of the window. The negative number does not work.

Why is it this way?

Probably because when somebody implemented the negative number support for the Split* methods they forgot to also do it for the SetSashPosition method.

ยทยทยท

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!