We are using the XamRibbonWindow and are using the Office2013 theme.
The keytip location for the ribbon tabs is set to be right on top of the captions of the tabs. I was able to successfully move the keytip to below the caption by re-templating/modifying the Infragistics style for the RibbonTabItem.
The issue is that the the keytip for the File tab didn't move. It is still located right on top of the caption. I get that the File tab is not considered a ribbon tab item and has it's own style. But no matter what I try I can't seem to move the keytip as shown in the picture.
Is there any way of moving the file tab keytip down like the other ribbon tab items.
Hello Michael,
Thank you for contacting Infragistics. The ApplicationMenu2010FileTab object is what you most likely need to re-template where presumably the "F" is coming from. I am guessing you've already re-templated the RibbonOffice2013.xaml file, which is where the ApplicationMenu2010FileTab is located. But I don't see how you would change this. I am curious how you are changing the position for the others. We don't make it easily accessible to change.
Hi Michael,
I used the Infragistics style for the RibbonTabItem to move the keytips.
<Style TargetType="{x:Type igRibbon:RibbonTabItem}">
In the ContentPresenter of this style I changed the IgRibbon:XamRibbon.KeyTipPlacementType property from "Caption" to "DropDownButton". When I did that the keytip moved down.
Honestly I was just trying things out to see what would happen and it worked.
<ContentPresenter x:Name="tabItemText" Width="Auto" HorizontalAlignment="Stretch" Margin="6,4,6,3" VerticalAlignment="Center" Content="{TemplateBinding Header, Converter={StaticResource stringWithoutMnemonicsConverter}}" ContentTemplate="{TemplateBinding HeaderTemplate}" ContentTemplateSelector="{TemplateBinding HeaderTemplateSelector}" igRibbon:XamRibbon.KeyTipPlacementType="DropDownButton" igWindows:ClippedTextToolTipService.AncestorTypeForToolTip="{x:Type igRibbon:RibbonTabItem}" igWindows:ClippedTextToolTipService.ShowToolTipWhenClipped="True" igWindows:ClippedTextToolTipService.ToolTipStyleKey="{x:Static igRibbon:XamRibbon.ToolTipStyleKey}" TextBlock.TextAlignment="Center" TextElement.Foreground="{DynamicResource {x:Static igRibbon:RibbonBrushKeys.TabNotSelectedTextFillKey}}"/>
Well that's what I did to get the 'H' and 'E' keytips to move down but I still can't get the 'F" keytip to move down.
So I'm still having the issue with the 'F' over the File caption and not below it.
Any suggestions?
Hello,
Sorry I misunderstood you. Look for the control template for ApplicationMenu2010Item Style. It's also set to
My apologies for not getting back to you sooner about this.
I tried the ApplicationMenu2010Item style but that didn't work for me. I tried a couple of other styles but still no luck on moving the 'F' keytip below the File caption.
I can't make it work on a small example either.
Anyway, you can see if you can get this to work on a small example?
I just want to know if it is possible to move that KeyTip.
Thanks
Mike
I will look into this some more this week.
I've discussed this over with the team and we've concluded that the keytips were never designed to be manipulated and the reasoning for the FileMenu to appear higher/overlapping was mostly to align with what MS Word was doing at the time we designed the Ribbon. Over the years we haven't tried to adjust it to mimic newer versions of Word (where the keytips align better in your favor). With that said, at this time, allowing users to move the keytips and/or properly aligning (if we consider this an needed improvement) them as a new default would be considered to be a new product idea.
You can suggest new product ideas for future versions (or vote for existing ones) at <www.infragistics.com/.../ideas>. Submitting your idea will allow you to communicate directly with our product management team, track the progress of your idea at any time, see how many votes it got, read comments from other developers in the community, and see if someone from the product team has additional questions for you. Remember when submitting your idea to explain the context in which a feature would be used and why it is needed as well as anything that would prevent you from accomplishing this today. You can even add screenshots to build a stronger case. Remember that for your suggestion to be successful, you need other members of the community to vote for it.
Let me know if you have any questions.