MFC Feature Pack - Accelerator issue - by asdfjcvn

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 540924 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 3/10/2010 8:03:44 AM
Access Restriction Public


If you add an accelerator to the accelerator table, compile and run the app, the added accelerator does not work.
The accelerator does its work when you reset it through the dialog "Customize->Keyboard->Reset All" provided by MFC.

This is some serious issue, because if the user doesn't see that the menu item has a default 
shortcut, he will never use it as intended. You cant tell your customers that they have to reset
their toolbars on an upgrade, only because you have added a new menu item which has a
default accelerator set.
Sign in to post a comment.
Posted by asdfjcvn on 5/4/2010 at 2:55 AM

i would not call it "few limitations" if i can not add a new accelerator to my application. Accelerators are one of the most common things in business software, through which the workflow is greatly enhanced. I do not see the advantage of customization if the developer looses all the control. This is how it works is a lame excuse to me for not implementing it properly. You take away features that were long ago in the libraries. Do you even do the basic tests on the crap that comes from BCG before replacing BCG with MFC in the classes?

Please guide me on how to add an accelerator to an existing application, so that i can use it without to reset the whole customization.
Posted by Microsoft on 5/3/2010 at 4:01 PM

Thanks for the report. This is by design, because the application menu/accelerator state is preserved in the registry. We do realize that there are a few limitations to the design but this is how the customization works.

Pat Brenner
Visual C++ Libraries Development
Posted by Microsoft on 3/10/2010 at 9:00 PM

Thanks for your feedback.

We are routing this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.