Hi, I'm using your (really) great XamRibbonWindow in my current project.
I'm starting the application with the application menu selected:
ApplicationRibbon.ApplicationMenu2010.IsOpen = true;
which works great. There is just one problem: the window buttons (minimize, fullscreen and close) are not displayed in the application menu when the application starts. When I navigate to a Tab, the window buttons are there. When I then navigate back to the application menu, the window buttons are there, too.
I'm encountering this problem using your sweet Office2013 theme:
<ribbon:XamRibbon DockPanel.Dock="Top" Theme="Office2013" ApplicationMenuMode="Office2010">
How can I make the window buttons visible on application start, too? (so that a user can close the application right away, if she/he wants to)
Hello,
Thank you for posting!
I have been looking into your issue and have created a small sample application in order to test the behavior you have reported. In the sample application I have a XamRibbonWindow with XamRibbon inside and ApplicationMenu2010. I set the IsOpen property of the ApplicationMenu2010 to true and the application works as expected.
I am attaching the sample application for your reference. Would you please modify it with the functionality you are using, so it reproduces the issue? This way I would be able to further investigate this matter for you.
Looking forward to hearing from you.
Hello Gergana,
to reproduce the issue using your sample you just have to add a RibbonWindowContentHost right inside the Grid:
... <igRibbon:RibbonWindowContentHost> <igRibbon:RibbonWindowContentHost.Ribbon> ... </igRibbon:RibbonWindowContentHost.Ribbon> <Border x:Name="RootContent" Padding="10"> <TextBlock>This is the container for the actual content (a frame e.g.)</TextBlock> </Border> </igRibbon:RibbonWindowContentHost> ...
I used this following the sample "xamRibbon Window" from your Samples Browser 2014. Can you verify the issue? Best regards,
Kurt
Hello Kurt,
Thank you for the provided code snippet. I was able to reproduce the issue and have logged this behavior with our developers in our tracking system, with an issue ID of 204391. I have also created a support ticket on your behalf with number CAS-159568-V8K0N1 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.
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.