is designed to behave as close to the MS Office backstage as possible and that is why the behavior that you described (the content and the header parts scrolling together) was implemented. Therefore a single ScrollViewer
wraps all elements in the default Template
of the RadRibbonBackstage
As for your other question, once you have created your custom Template
for the RadRibbonBackstage
you do not need to change that template every time we have a new release, a change will be needed only if we introduce a breaking change. Such changes are very rare as we do our best to avoid forcing our customers to update their custom styles after an update. This is why I would recommend utilizing the implicit styling mechanism
to apply styles for our components in your solution. If you add our ResourceDictionaries
or the theme assemblies in your solution, you can create a custom style for the BackstageMenu
and base it on the default RadRibbonBackstageStyle
available within our style dictionaries. During an upgrade you can even update the Telerik ResourceDictionaries
or the theme assemblies, but your custom style will not be overridden and will still be based on the latest default style.
DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.