Hi,
In the AppMenu I have a list of recent documents. I prefix each document name with a number (from 1-9).
The following line of code allows the recent document when pressing the hot key number to work as if the recent document were clicked (As expected). However the number in not underlined to give the end-user a visul clue that it is a hot key. What needs to be done?
uxToolbarManager.Tools[fileKey].SharedProps.Caption = "&" + mrCnt.ToString() + " " + recentDocument.FileName;
Thanks
Rich
Hello Rich.
The nmemonics should be displayable on the Application Menu. I do see a fix from earlier this year that may be related to your issue. Have you verified that you have the lastest service release / hotfix installed for your current version of NetAdvantage?
Additionally, you may want to verify the operating system is not hiding the underlines until the Alt key is pressed. Accessing this option is different depending on your version of Windows: Windows XP Windows Vista
If you still cannot get the nmemonics to show, please let me know.
Thanks,
Chris
Hi Chris,
I have a totally opposite question.
I wonder how to disable this hotkey behavior in the Ribbonbar. Especially in the QuickAccessToobar area.
I have several ButtonTool controls defined and added into the QuickAccessToolbar. When press Alt, I can see hotkey 1, 2, 3 appearing as default value. How to get rid of this?
I'm using version 7.3.
Jun
Hello Chris,
I have tried the same test with .NetAdvantage 2009 Vol2 and there is still a problem, i.e. pressing Alt + Shift brings the keytips.
Also, I tried to change the keytips property to something else but still the predefined keys appear , 1.2.3 etc. show what is the use then of keytips property?
Have a nice day,
Emmanouel
Emmanouel,
For tools placed on The Quick Access Toolbar, the QAT overrides the KeyTip specified on the tool itself. This is by design. If you'd like the ability to specify the KeyTip for Tool on the QAT, I suggest entering a feature request to have this functionality added in a future release.
The issue with the Alt-Shift keystroke showing the KeyTips has been addressed and should be available in the next service release. I have forwarded this information on support department so you will be automatically notified when this service release has been made available.
If you require further assistance, please let me know.
Thanks a lot.
I will wait for the next release.
It appears that the service release containing this fix has just been released, before you could be added to the notification list.
How to get the latest service release - Infragistics Community
Note that there may still be an issue with the KeyTips showing if the ALT+SHIFT keys are pressed and released quickly (i.e. before the ShowKeyTipsTimer expires). As the interval on this timer is pretty short, it will most likely not be encountered often. However, I have requested that you now get added to the notification list for when this issue is resolved.
Thank you.
In my application, I have a similar problem with the ALT key. The users want to be able to write foreign characters, like ß for instance. To do so, they are used to typing "ALT + 225". This works, but it's not possible to continue typing, because the menus show letters and typing most probably causes one of them to activate.
I have just installed and converted my project to Infragistics 2009.2.
Is there any way to disable this response to a press on the ALT key? Or any other way of fixing this problem?
Thanks in advance.
Hello.
There is no way to disable the Alt functionality of the UltraToolbarsManager. However, I've tested this scenario on my system using the "United States - International" keyboard, and did not encounter this issue. Using the Alt-key on the right-side of the keyboard, I was able to enter the Alt-keycodes without the KeyTips being shown.
When an international keyboard is being used, the right Alt-key is processed for foreign characters and special symbols before the Alt key message before the Alt key message could be processed by our Message Filter.
If you are still encountering this issue, I would recommend verifying your scenario and entering a support submission so our Developer Support department can further investigate.