One of the features that seems to be lacking (or im not figuring out how to use) is around not allowing a ContentPane to shrink beyond a certain minimum size. Right now it seems to ignore the MinWidth and MinHeigth property, i can resize the splitter to hide my pane.
I've tried setting the MinWidth at various levels of the xaml around the pane (for example on its parent TabGroupPane, or SplitPane) but nothing works.
I posted a feature request for this now because I also need such a functionality:
http://ideas.infragistics.com/forums/192363-wpf/suggestions/6396949-xamdockmanager-allow-using-the-minwidth-property
Actually never mind :), you guys already answered this in anothe thread: http://forums.infragistics.com/forums/p/54464/281380.aspx#281380
Andrew,
Thanks for trying to help with this issue, but here is a real world problem i need to solve. I have a dock manager with a tab group on the left, a document in the middle, tab group on the right, and one pane spanning the whole bottom (as in its a thin vertical pane that is stretched horizontally.
Now the bottom pane sometimes has no data, but other times it could have a lot of data. Its a wrappanel being dynamically populated at startup. So when a lot of data appears at startup that pane takes over the entire screen vertically. This is in unacceptable level of user experience. Do you have any practical way to help me resolve this? Being that the wrappanel has a scrollviewer im just surprised its not using it so that it does not auto adjust.
Of course resizing one time manually fixes the issue for that runtime session but thats just not something i can take to the user.
I am following up to see if you have any further questions.
Thank you,Sam
Yes currently there is no way to specify a constraining width. The reason is that there is no way to propogate the MinWidth/MinHeight of an element nested somewhere within. So for example if you had set a MinWidth on the ContentPane that was within a TabGroupPane, neither the TabGroupPane nor the SplitPane would know about it - their MinWidth/MinHeight just reflects what has been set on them and since elements like the TabGroupPane may be retemplated and the template will determine how much "chrome" would be around the content (and that chrome could even change based on state via triggers/vsm) there really isn't any way for the tabgroup to try and calculate a min width/height considering the children nested within. WPF just uses the MinWidth/MinHeight during the measure to constraint the availableSize that is passed along to an element's measureoverride.