[wxpython-users] Re: Splitter window and TreeCtrl issues (0/1)

[Gertjan Klein]

Robin Dunn wrote:

>In other words, the minsize is not overriding the 
>sashpos, it is just preventing the sash from being sized any smaller 
>than that due to the tiny size of the splitter before the initial 
>layouts are done.

So if I understand correctly, the minsize setting is (initially, when
the splitterwindow is still very small) changing the sash position
because honouring 0 would make the (left) panel smaller than minsize? If
this is the explanation, I'd still call this a bug. The minsize setting
goes for both panels. Therefore, initially, if the left panel is too
small, the right panel will be too small as well. Changing sashpos might
make one better, but will then make the other worse.

I even looked at the C++ source code to see if I could fix this, but I
couldn't find out how/where to detect this special case. (Though I do
know C, I don't speak C++, so my chances were slim to begin with.) A
pity (for me), as I don't like the splitter window's resize behaviour
much and would have taken a stab at fixing that as well.

Anyway, thanks for persisting in explaining things to me, it is much
appreciated. 

One last thing: I haven't been able to make the sash itself visible, no
matter what combination of flags I've tried. (I once managed to make it
sort-of visible by making the two panes sunken, but I don't want to do
that as it is hideously ugly.) Is there a way to influence how the sash
is displayed that actually does something?

Regards,
Gertjan.

-- 
Gertjan Klein <gklein at xs4all.nl>