How to avoid default hot key generation of windows API in mfc?

Question

0.00/5 (No votes)

See more:

In my VC++ project i got an issue like this. ie, there is an edit box which accepts string input from user. while pressing another button, this string will be set on a Button. to set this text on this button iam using

C++

SetWindowText()

API. But the issue was when user enter the input like this
"&abcd" then "&" will not be set on button. It will make "a" as hot key. ie,
now the text will be displayed on button like this "abcd". How can i avoid default hot key conversion of windows API? Is this possible? If yes give me a reply.

Posted 4-Mar-13 2:21am

SajeeshCheviry

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Manfred Rudolf Bihy · Accepted Answer · 2013-03-04T02:33:00

Solution 1

You have two options to avoid having the ampersand generate a hot key:
1. Remove all ampersands from the string: &button -> button
2. Make sure that single ampersand instances inside the string are doubled: &button -> &&button
The first ampersand escapes the second one and only one ampersand is displayed.

Regards,

— Manfred

Posted 4-Mar-13 2:33am

Manfred Rudolf Bihy

Updated 4-Mar-13 2:35am

v2

Comments

SajeeshCheviry 5-Mar-13 0:02am

Thanks for your support

Jochen Arndt · Accepted Answer · 2013-03-04T06:15:00

Solution 2

Besides the options mentioned by Manfred in solution 1, there is a third one:
When using owner draw buttons (see the MSDN example at CButton::DrawItem()[^]), the DrawText() format flag DT_NOPREFIX will disable processing of prefix characters and show the text as it is.

Posted 4-Mar-13 6:15am

Jochen Arndt

Comments

SajeeshCheviry 4-Mar-13 23:40pm

Thanks for your support. I have another doubt. Can i use ModifyStyle to avoid such a problem?
ie,
m_button.ModifyStyle(0, DT_NOPRIFIX);
m_button.SetWindowText(csText);

Jochen Arndt 5-Mar-13 2:57am

No. DT_NOPREFIX is a format flag for DrawText() and not a button style. The value is 0x800. When setting this for a button style, the text will be drawn at the bottom of the button (style BS_BOTTOM). See button styles in the MSDN: http://msdn.microsoft.com/en-us/library/tf9hd91s%28v=vs.80%29.aspx.