Hi.
I'm currently evaluating the XamRibbonWindow. I'm not actually using the Ribbon, just using it as a container in order to take advantage of the Office 2013 theme.
I create the RibbonWindow, set it's content to the RibbonContentHost, and then set my user control as the content of the RibbonContentHosts' content (sorry for the nesting !).
Anyway, the window has size to content set to width and height. My usercontrol is 600px wide, but on opening the window, the window is 614 pixels wide. The user control has an expander. When it's expanded, the window height adjusts (as expected), but then the width adjusts to 600 pixels, giving the illusion that the window is skipping a few pixels to the left.
Is this a bug ? The stock WPF window doesn't exhibit this behaviour. I've also been evaluating Telerik's Window, which also doesn't exhibit this.
Quick update :
The User control has a scroll viewer inside it (technically, scroll viewer resides within a content control, which is hosted by a usercontrol, hosted by the RibbonWindowContentHost ...). It seems that the initial dimensions of the window are what they would have been if the scroll bar was visible (accounting for the extra 14 pixels, or thereabouts), but rather than allowing the scroll viewer to shrink its content, the window expanded.
Hi Michael,
Thank you for your post. I have been trying to reproduce your issuer and on side it seems that everything is rendered as expanted.
I am attaching a sample application(RibbonWindow_UserControl.zip) that follows your scenario.
Please let me know, if I am missing something.
Looking forward to hearing from you.
I've modified your sample project to be more in line with what my application is doing - the key differences :
If you click on the expander, you will observe the window flicker a little, and all the controls appear to move to the left a few pixels. I clicked the expander in its dead center. After the click, the mouse pointer is no longer in the same position. Even resizing the window will re-produce this.
Thank you for your post. I have been looking into your concerns and this fix is included in the latest Service Release of vol. 14.2(14.2.20142.2024). You can download the Service Releases by logging to our web site and going to Account\My Keys and Downloads.
Let me know, if you need any further assistance on this matter.
Just updated to 14.2.20142.1000, and the issue is still there.
Hello,
We have shipped out a new service release where your issue is resolved. I'd be glad to find out if you had tested it out and if it had met your requirements.
You can download the Service Releases by logging to our web site and going to Account\My Keys and Downloads.
Hello Michael,
I have logged this behavior with our developers in our tracking system, with an issue ID of 178897. I have also created a support ticket on your behalf with number CAS-142291-T3K2B3 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.
Anyone ?
Should I raise a support request ?