I noticed in the Recent Documents sample that the file numbers (1-9) had access keys assigned. I've added the control and logic to our client and our numbers don't have access keys. I've added our XAML below.
The main difference is that, instead of performing a "manager.Documents.Add(docRef);" for each file, we're serializing and deserializing - our load is as follows: "this.recentDocManager.Deserialize(recentDocuments[0].PreferenceData);". Is there something else we need to define?
The main difference is that, instead of performing a "manager.Documents.Add(docRef);" for each file, we're serializing and deserializing - our load is as follows: "this.recentDocManager.Deserialize(recentDocuments[0].PreferenceData);". Is there something else we need to define?
<!--Define Application Menu-->
<actr:Ribbon.ApplicationMenu>
<actr:ApplicationMenu AutomationProperties.AutomationId="appMenu">
<!-- Additional Content (Right side of application menu) -->
<actr:ApplicationMenu.AdditionalContent>
<actr:RecentDocumentMenu x:Name="recentDocMenu" Label="Recent SR's" Width="300">
<shared:RecentDocumentManager x:Name="recentDocManager" MaxDocumentCount="12" MaxFilteredDocumentCount="10"/>
</actr:RecentDocumentMenu>
</actr:ApplicationMenu.AdditionalContent>
<actr:ApplicationMenu.FooterButtons>
<actr:Button AutomationProperties.AutomationId="buttonOptions"
Command="{StaticResource OptionsCommand}"
KeyTipAccessText="I" />
<actr:Button AutomationProperties.AutomationId="buttonExit"
Command="{StaticResource exitCommand}"
KeyTipAccessText="X" />
</actr:ApplicationMenu.FooterButtons>
</actr:ApplicationMenu>
</actr:Ribbon.ApplicationMenu>