Hi,
I am having a problem with the radsplitbutton in a custom user control. We have defined the look and feel in generic.xaml and have a drop down menu in the header/title. If I use the raddropdownbutton it works perfectly, but we decided that it would be nice to use the split button so that the most commonly used item can always be easily clicked without having to drop down the menu list.
We simply replaced RadDropDownButton with RadRibbonSplitButton and RadDropDownButton.DropDownContent with RadRibbonSplitButton.DropDownContent, but kept the exact same RadContextMenu. When we do that we get an out of memory exception before the controls are rendered. Is this a bug? Or are we doing something incorrectly?
This functionality is not critical to our product, but thought it would be worth pointing out - please let me know if we are using the controls incorrectly or if you require any further information.
Thanks!
Nathan
I am having a problem with the radsplitbutton in a custom user control. We have defined the look and feel in generic.xaml and have a drop down menu in the header/title. If I use the raddropdownbutton it works perfectly, but we decided that it would be nice to use the split button so that the most commonly used item can always be easily clicked without having to drop down the menu list.
We simply replaced RadDropDownButton with RadRibbonSplitButton and RadDropDownButton.DropDownContent with RadRibbonSplitButton.DropDownContent, but kept the exact same RadContextMenu. When we do that we get an out of memory exception before the controls are rendered. Is this a bug? Or are we doing something incorrectly?
This functionality is not critical to our product, but thought it would be worth pointing out - please let me know if we are using the controls incorrectly or if you require any further information.
Thanks!
Nathan