Today, we announced the roadmap for the WPF platform. The post defines the areas of investment in future releases of WPF, and details the current progress of improvements made to the WPF platform in the .NET Framework 4.6 and Visual Studio 2015.
Every now and then we get some really good questions that make us think. This was one of those questions. Here was the original Tweet that was sent our way.
For those of you unfamiliar with the context of the question,
WPF exposes a swatch of colors that comprise the current Windows system theme. These are available in the SystemColors class as Colors, Brushes, and corresponding ResourceKeys (for binding with dynamic notification of changes to these colors, e.g. if the user switches Windows themes).
For those targeting .NET 3.5, you will notice that RibbonWindow’s Height, Width, Left, and Top properties are a little funky and can be misreported. This article explains why RibbonWindow on .NET 3.5 has these issues, how the issues manifest, and how to work around them.
The Ribbon RTM release was built against .NET 3.5, but our October 2010 release of Ribbon includes both .NET 3.5 and .NET 4.0 Ribbon DLLs. With the v4.0 Ribbon, we have enabled ClearType on all of the Ribbon controls using RenderOptions.ClearTypeHint. WPF applications using RibbonWindow must also opt-in to enable ClearType for all content below the Ribbon.
I’m sure many of you are wondering what the future of the WPF Ribbon will look like. The future is hard to predict and there are so many things that can change. But here is a short list of things we will be looking into for the future of the WPF Ribbon.
Here is the detailed list of the items that were fixed in the October 2010 update.
Ribbon Split Button is only half-highlighted when users mouse over the button
Ribbon Title is bottom-aligned, should be centered
Ribbon Quick Access Toolbar icons are clipped and top-aligned
Ribbon Contextual Tab header text is getting truncated if too long
Ribbon Gallery Item does not stretch to fit its Parent Panel
Initial enabled state of Ribbon Split Menu Items can be incorrect if they have children
Ribbon Split Menu Item with sub-items is disabled if CanExecute=false
WPF Ribbon Dropdown does not close when CanAddToQuickAccessToolBarDirectly=”False”
Here is the October 2010 update for the Microsoft Ribbon for WPF. This update contains the latest product changes and fixes for the WPF Ribbon. You can download the latest ribbon here.
We’ve made a few changes to the WPF Ribbon you might be interested in…
We have received a query about being able to hide the title panel in a Ribbon Browser Application. As always this can be achieved by finding the appropriate element within the Ribbon template and manipulating its Visibility. The attached project demonstrates this approach.
We have received some feedback about the blurriness of the images in the Ribbon sample that was published alongside the Ribbon release. We would like to clarify that the sole purpose of this sample application is to showcase the API capabilities for the Ribbon Control Library.