Solution

How string id's are generated in RC files

RC files can include many header files, with resource.h being one of these files.

In order to avoid the requirement to access all source code files in the development environment, Alchemy Catalyst ignores the value of the ID and uses a hashed value of the text for the ID.

This is where the string id's that you see in the Alchemy Catalyst UI for RC files comes from. You can see an example of this in the screenshot below.

This is a very effective way of dealing with string id's in an *.rc file and means Alchemy Catalyst relies simply on the *.rc file itself.

Although very effective it has the drawback of not displaying the more descriptive id that may be available in the header file.

It is not advisable to change the mechanism for the ID if you already have been localising  your files in Alchemy Catalyst, as it would result in inaccurate leverage from that point forward due to IDs not matching with previous TTKs.

If the ids in an RC file are changed between builds then you will get a For review status for a string with a changed id even though it was previously signed off. Due to this change in ID Alchemy Catalyst will not be able to carry over the Signed Off status, Lock, Memos etc. during leverage.  

 

Related topics

 

Products or Versions Affected

  • Alchemy CATALYST 7.0  and greater