how to convert string to resource ID

[KingsGambit]

Intead of "IDS_VALUE", you can keep the actual integer values like "2344" in the XML file. And you can easily convert the "2344" to 2344 by using atoi().

[ronovice]

this was an idea, but i want to keep the xml file readable. if a tag is 2344 instead of NAME (e.g.), it will be difficult to do that.

[lxkjlzz]

Directly to put forward a corresponding relationship between int an string :-D

[CPallini]

You should maintain both the string value and the corrensponding numeric one inside the XML file. IMHO you've no way other than parsing the resource.h in order to decode the string (BTW why are you building a XML replica of the resource.h file?). :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke
[My articles]

[ronovice]

Thank you. I will use a map eventually (the xml file will remain the same). There is a strong relation between stringtable values in resources and the data from the xml file, but is not a replica :).

[KingsGambit]

Using a map would be fine.

[Lost User]

You can also use strings rather than integers to refer to your resource items. If you do not give resource names a #define value, then you can refer to them by the name as string value, rather than its integer equivalent.

[cmk]

Not possible. IDS_VALUE is a #define, these are resolved by the preprocessor and are not preserved as strings anywhere in the object files.

...cmk The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying. - John Carmack

[ronovice]

i dont't want to use #define because i use stringtables for different languages. a map seems to fit to my needs.

[ronovice]

thanks! it was worth a try! i will use a map (as the best idea for the moment)!

[Lost User]

ronovice wrote:

i dont't want to use #define

That is what I was trying to explain in my previous post. If you do not use #define then the resource names can be accessed by their actual name as extracted from your XML, no need for a map or any other type of transform.

[Lost User]

cmk wrote:

Not possible.

Untrue; if you do not equate a resource name to an integer value, then you can address it by the actual string name. [edit]My apologies, this does not hold true for STRINGTABLE entries.[/edit]

modified on Thursday, January 7, 2010 8:12 AM

[ronovice]

i wanted to use LoadString method which will need as parameter a UINT, but i have only the string . How can I get from resources the text associated with that UINT if i cant convert the string to UINT ID? if there is another solution(even without using LoadString), I will gladly use it.

[Lost User]

You could try using FindResourceEx()[^] rather than trying to access it directly. This should allow you to use the name as a string and also to select which language you wish the string to be in. [edit]My apologies, this does not hold true for STRINGTABLE entries, although you could possibly use a user defined resource type.[/edit]

modified on Thursday, January 7, 2010 8:14 AM

[KarstenK]

write in the resource file IDS_VALUE "IDS_VALUE" oh my god :doh: :doh: :doh:

Press F1 for help or google it. Greetings from Germany

[cmk]

Yeah, RT_STRING's screw things up, you can't even FindResource() on them without jumping through hoops. e.g. Given: IDS_STRING as a String Table entry // Fails hnd = FindResource(mod, MAKEINTRESOURCE(IDS_STRING), RT_STRING); // Works id_string = MAKEINTRESOURCE((LOWORD(IDS_STRING)>>4)+1); hnd = FindResource(mod, id_string, RT_STRING); ... let alone getting the size, or loading the string without using LoadString().

...cmk The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying. - John Carmack

[ronovice]

Thanks. i will try this!

[Lost User]

I really must take my own advice, and test everything before posting suggestions. :mad: