Let me explain why we created the RadRibbon
controls. The main reason for creating separate buttons for the RadRibbonView
is the resizing feature
. We needed properties like Size
(and others) which are now directly related with the resizing feature. You need to keep in mind that all the controls designed for the RadRibbonView
has their IsTabStop
property set to False
. This is the main difference (in their native properties) between the controls that are not designed for the RadRibbonView
With the current implementation of the RadRibbonView
you are allowed to visualize controls that are not specifically designed for the resizing feature of the ribbon. This means that if you define RadSlired
(in other words - controls not designed to be used in the RadRibbonView
) controls in one RadRibbonGroup
. That group will go from its Large
state directly in its Collapsed
state - the resizing will be ignored.
For the moment of writing we do not have any plans to significantly change the current implementation of the RadRibbonView
I hope that this information clarifies all of your questions.
Pavel R. Pavlov
TRY TELERIK'S NEWEST PRODUCT - EQATEC APPLICATION ANALYTICS for WPF.
Learn what features your users use (or don't use) in your application. Know your audience. Target it better. Develop wisely.
Sign up for Free application insights >>