Exception using access text to go to the backstage

[Steve]

We recently (a few months ago) switched from Q3 2017 to R1 2019 SP1, and traced the origin of this exception to switching to the new version. I.e. it did not have this issue with the older version.

We are using implicit styles and it only happens in the 2013 theme, at least among the themes that we use.

 

If we press Alt, and then "F" to get to the backstage, we get the following exception. After the exception everything works normally, but you have to press Alt again to get the access text to show on the backstage.

 

Object reference not set to an instance of an object.

Stack Trace:
   at Telerik.Windows.Controls.RibbonView.KeyTipService.<ShowBackstageItemsTips>b__48()
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

[Steve]

I should clarify that it is the Office 2013 theme that we are using.

[Dinko]

Hi Steve,

Thank you for the provided steps.

I have followed them but wasn't able to get such exception on my side. I have tested with the mentioned version and with the latest one: no difference on my side. I think I may miss some additional code from your implementation. Attached to this reply you can find the sample project which I used to test your scenario. Can you go through this sample solution and let me know what I need to modify to mimic your implementation which reproduce this exception.

Regards,
Dinko
Progress Telerik

[Jennifer]

I work with Steve and he asked me to look at your example.  The difference is that your example doesn't have any AccessText on the backstage items (e.g., Save).  Once I added it to one of them in your example, I got the same exception.

[Dinko]

Hi Jennifer,

Thank you for the provided additional information. 

I manage to reproduce this exception, therefore I have logged it in our Feedback Portal where you can track its progress. I am happy to inform you that our development team is currently investigating this exception. You should expect a fix in one of our next LIB. The feedback item will be updated with the version in which it will be available.

I have updated your Telerik Points for bringing this behavior to our attention.

Regards,
Dinko
Progress Telerik