I''ve built an app using XPMenus, a TabbedMDIManager, a DockingManager and a GridControl.
In general, everything works fine, with one exception: A while ago the menu accelerators
stopped working, and I can''t figure out what I changed to trigger that.
In my app, the focus is usually in the GridControl. If I click, say, Alt+W to
invoke the &Window menu, nothing happens other than a "ding". Oddly, if I press
AND LET GO OF the Alt key, then the XPMenu DOES get the focus - I can then press W to
drop down the &Window menu. But users probably won''t think of doing it that way.
My GridControl shares its MDI Form with a Panel, and the Panel does have one hotkey
of its own. That hotkey works as expected.
Forgot to mention: I''m using version 188.8.131.52, and upgrading right now isn''t an option.
ADAdministrator Syncfusion Team November 3, 2004 06:41 AM
I am afraid, this information is not sufficient to determine the cause for this behavior. Please refer to the test sample attached here. Can you see this behavior in this sample on your machine ? If not, could you please modify it to show the problem and send it back to us so that we could further investigate this issue ? A test sample is very helpful in this scenario since it is almost impossible fix something without a sample to recreate it.
Also, v184.108.40.206 is over six months old, and several bug fixes/enhancements have been performed on the XPMenus and the docking windows framework since then. Therefore we strongly recommend you to upgrade to v220.127.116.11. We appreciate your cooperation and understanding on this issue.
ADAdministrator Syncfusion Team November 3, 2004 06:45 AM
The test sample was not uploaded correctly in my previous update. Sorry about that. I have re-attached it here.
TJTJNovember 3, 2004 09:44 AM
I tried the sample app you provided, and made two small changes:
1) Converted it to .NET 1.1
2) Added IsMainMenu to the toolbar''s BarStyle.
With those changes, it exhibits the same behavior I''m seeing in my app. That is,
Alt+W doesn''t activate the menu item (whether the focus is in the GridControl or
the Panel), whereas pressing and releasing Alt does activate it.
I''m sure 18.104.22.168 is a compelling upgrade, but at the moment we''re quite close to
releasing our product, so I''m reluctant to upgrade if I don''t need to. However,
if it fixes this issue, I might...
Thanks for your help,
ADAdministrator Syncfusion Team November 5, 2004 04:25 PM
Thanks for the update. I was able to see the above mentioned issue in my sample, and I am afraid, this error exists in v22.214.171.124. However, I have notified the development team about the same, we have logged a QA report#668 in this regard. We will try our very best to address this issue at the earliest and include the fixes in our future releases. We appreciate your feedback and thanks for choosing Syncfusion products.
ADAdministrator Syncfusion Team November 17, 2004 08:57 AM
This issue has been taken care of internally, and the fixes are expected to be incorporated in the v3.0 final release. We appreciate your continued interest in Syncfusion products.
ADAdministrator Syncfusion Team November 23, 2004 03:42 PM
Is this the same issue we are seeing with the XP Toolbar shortcuts not firing when shortcuts are assigned to buttons?
>This issue has been taken care of internally, and the fixes are expected to be incorporated in the v3.0 final release. We appreciate your continued interest in Syncfusion products.
ADAdministrator Syncfusion Team December 2, 2004 06:06 PM
This problem discussed in this thread is not the same as the XPToolBar Shortcut issue. But we have an open QA report# 708 in this regard, and we will try our very best to address this issue at the earliest. We appreciate your patience and cooperation.