A few versions ago, you implemented the mechanism where the KeyTipAccessText text will be underlined in the menu text. It is my understanding that you look for the first capital letter, otherwise, the first lowercase letter. 99.9%, that works well.
I have a menu item with the text "Page Right". The 'R' is already taken by another "right" item, so we went with 'G' for the KeyTipAccessText.
We get "Pa_ge Right", although our intention was to get "Page Ri_ght" since that would make more sense.
Does your algorithm have any allowances for allowing us to mark which instance of the letter we want for the rare instances where your default algorithm misses?
Perhaps expand your algorithm to check if the letter is preceded by an underscore, and then use that instance? Even something cheezy like "2G" to use the 2nd G would work.
I have a menu item with the text "Page Right". The 'R' is already taken by another "right" item, so we went with 'G' for the KeyTipAccessText.
We get "Pa_ge Right", although our intention was to get "Page Ri_ght" since that would make more sense.
Does your algorithm have any allowances for allowing us to mark which instance of the letter we want for the rare instances where your default algorithm misses?
Perhaps expand your algorithm to check if the letter is preceded by an underscore, and then use that instance? Even something cheezy like "2G" to use the 2nd G would work.
