Hi.

> you have to add a scroll container to make the scrolling available: 
> http://tinyurl.com/32l7v2a

I looked at what you added to the code. It just proves my point. If you want 
splitters and tabviews to behave properly when used together, you need to add a 
scroll inside each tab page. Look at the example you provided. No matter how 
you shrink the window horizontally, a horizontal scrollbar will not appear even 
if the second pane of the splitpane disappears completely from view. Sometimes, 
when you shrink the window enough, you get scrollbars both inside the 
individual panes of the inner most sp litpane and inside the second tab page of 
the main tabview. There's no easy way to predict what will be scrollable under 
what circumstances.

We solved the problem by completely elliminating the outer scroll container, 
placing the main tabview directly inside the window, by placing a scroll inside 
each pane of the split pane and setting a minimum width and height on each  
container inside the scroll containers. Still, this is a workaround, IMO, to a 
bug that splitters have. I did not do any experiments with other widgets placed 
in splitters, but I do seem to recall that when using tables instead of 
tabviews inside splitters these properly handled resizing and minimum size 
constraints.

What happens, IMO, is that splitpanes do not communicate properly with 
contained elements, thus not passing minimum height and width to containing 
containers. As a consequence, they resize to whatever their container tells 
them to resize, in spite of breaking minimum size constraints on contained 
widgets. If you take out the additional (inner) scrolls, maybe place some 
additional widgets in the tab pages, and look at widget sizes with the 
inspector, you'll see that even if child widgets do not shrink, the splitters 
containing them do. It is normal that splitters do not show scrollbars of their 
own free will, but IMO it is  not normal that they shrink more than inner 
controls would like to allow.

My only (remaining) problem is th is: is there something I do not understand 
about splitters, or should  I file a bug report?

br,

flj


------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to