MFC dialogs: manual edit *.hm file - range and numbering of items

Question

1.00/5 (1 vote)

See more:

Hi!
I have to manual edit a *.hm file which contains all the help ID´s

We have "inherited" a punch of code with dialog resources and help files.
The dialog resources (.rc, .h,) had to be edited by hand, so no resource editor available which can create a help-ID file

The resourcefile has the help ID attached at the end of each control like:

C#

EDITTEXT        IDC_SIZE_VARIANTS_CATEGORY_NAME,57,9,130,14,ES_AUTOHSCROLL,0,HIDC_SIZE_VARIANTS_CATEGORY_NAME

and nameing is done by adding "HI" prefix - so no problemn to do this

But how does the numbering in the .hm file work?

we have 2-byte numbers like
#define HIDC_WINGFRAMETHICKNESS 0x3ebd // IDD_WINGPROPDLG

and 4 byte number like
#define HIDC_ROKAEX_PROFILE_TYPE 0xc0064007 // IDD_ROKAEX

also the numbers are not in order...

What is the best way to get correct numbers in the Help-ID file without using the resource editor?

many thanks in advance!

What I have tried:

serached the web and MFC MSDN (the answer there does not fit to my problem)

Posted 19-May-16 0:54am

FriendOfAsherah

Add a Solution

Comments

Sergey Alexandrovich Kryukov 19-May-16 9:23am

Not clear. What is not in order? What order should be there and what you get?
—SA

Richard MacCutchan 19-May-16 12:50pm

The numbers are generated by one of the wizards used by Visual Studio. If you change them then it is quite possible your code will break somewhere else. Only change them if you are going to recompile everything that is part of the project.

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)