Hi,
I'm running into some issues using the KeyTipService with the RadRibbonView.
The first issue is that if the ribbon is minimized, the key tips seem to display most of the time, without popping up the ribbon tab. (See attached picture). I say most of the time, since once in a while it will actually work (the ribbon tab will open), but then sometimes after it does work (the ribbon tab opens), it might not close afterwards! (e.g., if the user clicks the application title bar instead of choosing a key tip).
The second issue is that when the ribbon is NOT minimized, the key tips seem to work pretty well, except for an annoying focus rectangle that I cannot seem to get rid of when displaying a menu (see attachment). I have tried setting IsFocusable to false and the like, but still can't get it to stop showing. Any tips on how to get rid of that focus rectangle (using RadContextMenu and RadMenuItem).
Finally, when the key tips do display, they display very slowly. i.e., when using ALT, then picking a tab, the key tips on that tab take a long time to display. So much so that you can see them pop up, gradually, from left to right. At first I thought it was a deliberate animation, but seeing that Office and other applications show the key tips instantaneously, I am wondering whether it's just a performance issue, because if the key tip the user wants is to the far right hand side, then they have to wait a couple of seconds to see it.
As for these three issues, the one I am most concerned about is the flaky behavior with key tips when the ribbon is minimized, because it looks out of place and users will have a difficult time trying to navigate it. They shouldn't have to have the ribbon maximized in order to use key tips.
Kind Regards,
Wayne.
8 Answers, 1 is accepted
Thank you for contacting us.
Usually the dotted border that you want to remove is coming from the FocusVisualStyle property of the element defined in xaml. That why by setting the FocusVisualStyle to "{x:Null}" of the menu should remove that problem.
As for the other issues we have tried to reproduce them but without success. Could you please provide us with a sample project reproducing the issue or at least the xaml file of your ribbon. Doing so we will be able to further investigate the issue.
Looking forward to hearing from you.
Kind regards,
Kiril Vandov
Telerik
Hi Kiril,
Setting FocusVisualStyle to null is one of the first things I tried and it doesn't work. The focus rect is still displayed (when using key board access). A minor issue in the scheme of things though, but it would be nice to find a solution.
As for the other issues, I cannot provide any xaml since in our production implementation there is no xaml. None. In my prototype implementation there is only xaml to put the ribbon on the parent form. In both cases, everything else is implemented by an adapter API.
If I get time I will try to reproduce the issues (pop up not displaying some of the time and the performance issue) in an independent sample application.
The 4th issue that I posted (key tips falling behind the tab pop up, I also observe in a program developed by my company, but 100% independently of my work, so that one should definitely be reproducible, since I can reproduce it and other people in my company have independently reproduced the same problem).
Regards,
Wayne.
If settings the FocusVisualStyle to null does not solve the issue means that the problem is not from the menu itself. We have further investigated the reported behavior and we have found that this visual rect is the focus visual of one of the items in the Default style of the RadRibbonDropDownButton, the ("DropDownPopupContent") element. Until we fix this element FocusVisual in the default style the only way to remove it is by creating a custom style for the RadRibbonDropDownButton and setting FocusVisualStyle to null to the "DropDownPopupContent" element.
As for the issue with falling KeyTips behind the tab, we have tried to reproduce the issue on our side but without success. That is why I would like you to provide us with a project reproducing the issue to further investigate it.
Looking forward to hearing from you.
Kind regards,
Kiril Vandov
Telerik by Progress
Hello Kiril,
I am having same problem with FocusVisualStyle of DropDownContent. Hopefully there is a solution to remove the dotted rectangle focus style. Setting FocusVisualStyle to null doesn't work. and i have also tried telerik:DropDownButtonExtensions.FocusContentOnOpen="False" with no success.
Many Thanks,
Arif
I am attaching a sample project demonstrating the approach suggested by colleague Kiril of setting FocusVisualStyle to null on the "DropDownPopupContent" element inside the template of the RadRibbonDropDownButton. Please, note that I have extracted the template for the Fluent theme. I have included a comment in the attached project to indicate where I have made changes to the template.
If you are using a different theme, you will have to extract and modify the template for the correct theme. Additionally, the recommended approach for modifying control templates is by using implicit styles with the NoXaml binaries.
I hope this helps.
Regards,
Vladimir Stoyanov
Progress Telerik
Thank you Vladimir,
Later i had tried the solution and it does work. However this would be the only control in our application where we are customizing the default template (so for now, we are going to carry this issue in our builds). Hopefully there be a fix in default template soon.
Regards,
Arif
I have logged this behavior in our feedback portal: RibbonView: The DropDownPopupContent inside RadRibbonDropDownButton has a default FocusVisualStyle. You can follow the item in order to get notified for any developments.
What I can suggest as an alternative to modifying the template is to add an implicit style targeting ContentControl and set the FocusVisualStyle to null there. Please, note that since the ContentControl is in a Popup, you will have to add the style in the App.xaml file of the application.
Should you have any additional questions or concerns, do not hesitate to contact us again.
Regards,
Vladimir Stoyanov
Progress Telerik