WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
attached is a script that illustrates the problem:
2 splitter windows, one inside the other.
The splitters don't honor the MinimumPaneSize setting.
Dragging the horizontal splitter down lets the blue panel with a heigth of about 6 pixels when it should have been 10. Same problem can be noticed if you drag the vertical splitter to the far right... 6 pixels instead of 10.
WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
attached is a script that illustrates the problem:
2 splitter windows, one inside the other.
The splitters don't honor the MinimumPaneSize setting.
Dragging the horizontal splitter down lets the blue panel with a heigth of about 6 pixels when it should have been 10. Same problem can be noticed if you drag the vertical splitter to the far right... 6 pixels instead of 10.
It's probably using the sash position for the size calculations instead of the actual window size, and since the sash has width you end up a few pixels off.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
What would be the best approach to fix this problem? factor in the sash size? is the sash the same width everywhere? is the sash size a wx constant?
Actually I thought this to be a bug... is it a bug? could it be easily fix?
···
On Wed, 15 Sep 2004 10:00:06 -0700, Robin Dunn <robin@alldunn.com> wrote:
Peter Damoc wrote:
WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
attached is a script that illustrates the problem:
2 splitter windows, one inside the other.
The splitters don't honor the MinimumPaneSize setting.
Dragging the horizontal splitter down lets the blue panel with a heigth of about 6 pixels when it should have been 10. Same problem can be noticed if you drag the vertical splitter to the far right... 6 pixels instead of 10.
It's probably using the sash position for the size calculations instead of the actual window size, and since the sash has width you end up a few pixels off.
Peter Damoc wrote:
> WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
> attached is a script that illustrates the problem:
> 2 splitter windows, one inside the other.
> The splitters don't honor the MinimumPaneSize setting.
> Dragging the horizontal splitter down lets the blue panel with a heigth
> of about 6 pixels when it should have been 10. Same problem can be
> noticed if you drag the vertical splitter to the far right... 6 pixels
> instead of 10.
It's probably using the sash position for the size calculations instead
of the actual window size, and since the sash has width you end up a few
pixels off.
This is exactly it -
I have a patch on SF that I seem to have misfiled under bugs instead
(probably why it never really got looked at) from quite some time ago
that should fix this (and did/does for me).
On Wed, 15 Sep 2004 10:00:06 -0700, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
attached is a script that illustrates the problem:
2 splitter windows, one inside the other.
The splitters don't honor the MinimumPaneSize setting.
Dragging the horizontal splitter down lets the blue panel with a heigth of about 6 pixels when it should have been 10. Same problem can be noticed if you drag the vertical splitter to the far right... 6 pixels instead of 10.
It's probably using the sash position for the size calculations instead of the actual window size, and since the sash has width you end up a few pixels off.
What would be the best approach to fix this problem? factor in the sash size?
Probably.
is the sash the same width everywhere? is the sash size a wx constant?
No, a platform-specific renderer is used to draw it, but the renderer knows the width it will use, and that is wrapped in splitter.GetSashSize()
Actually I thought this to be a bug... is it a bug? could it be easily fix?
I'll take a look.
···
On Wed, 15 Sep 2004 10:00:06 -0700, Robin Dunn <robin@alldunn.com> wrote:
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
On Wed, 15 Sep 2004 10:00:06 -0700, Robin Dunn <robin@alldunn.com> wrote:
Peter Damoc wrote:
WinXp SP1 wxPythonWIN32-2.5.2.9pu.20040910-Py23
attached is a script that illustrates the problem:
2 splitter windows, one inside the other.
The splitters don't honor the MinimumPaneSize setting.
Dragging the horizontal splitter down lets the blue panel with a heigth
of about 6 pixels when it should have been 10. Same problem can be
noticed if you drag the vertical splitter to the far right... 6 pixels
instead of 10.
It's probably using the sash position for the size calculations instead
of the actual window size, and since the sash has width you end up a few
pixels off.
This is exactly it -
I have a patch on SF that I seem to have misfiled under bugs instead
(probably why it never really got looked at) from quite some time ago
that should fix this (and did/does for me).