The Resource Symbols Dialog box uses the first named value, rather than the value actually used in the rc file when showing editing symbol values.
This prevents you deleting unused symbols, and encourages you to delete symbols which are in use.
This is the state you end up in if you import a new bitmap, and a new name is generated, and then you rename the bitmap ID in the properties pane to one that comes alphabetically after the generated symbol.
IDB_BOGUSHELP BITMAP "res\\bogushelp.bmp" IDB_BITMAPUP BITMAP "res\\up.bmp" IDB_BITMAPINSERT BITMAP "res\\insert.bmp" IDB_BITMAPDELETE BITMAP "res\\delete.bmp" IDB_BITMAPDOWN BITMAP "res\\down.bmp" IDB_BITMAPDETAILS BITMAP "res\\details.bmp" IDB_BITMAPOPTIONS BITMAP "res\\options.bmp" IDB_GENERATE BITMAP "res\\cog.bmp" IDB_BITMAPEDIT BITMAP "res\\edit.bmp"My resource.h file has the following definitions:
#define IDB_BITMAP2 151 #define IDB_BITMAPUP 151 #define IDB_BITMAP4 153 #define IDB_BITMAPINSERT 153 #define IDB_BITMAPDOWN 155 #define IDB_BITMAP7 156 #define IDB_GENERATE 156 #define IDB_BITMAP8 157 #define IDB_BITMAPEDIT 157 #define IDB_BITMAP9 158 #define IDB_BITMAPDETAILS 158 #define IDB_BITMAPOPTIONS 159
http://i4.tinypic.com/10458ux.png
As you can see from the image here, the editor clearly thinks that IDB_BITMAP2 is in use, and shouldn't be deleted, despite it showing as not in use further down. In addition, the used by correctly states it's used by IDB_BITMAPUP!
Why won't it let me delete IDB_BITMAP2, and mark IDB_BITMAPUP as in use.
I'm reposting this here, after being told here:
that it won't be fixed, and that I should post here instead (not that I really understand that logic, but maybe someone at microsoft can enlighten us on that statement too).
Resource Symbols Dialog Box fails with duplicate values
Scott Herbert
Whenever I have problems with the resource editor and suchlike, I will always just edit the resource.h/rc file manually.
These files are complex - as you know - and the resource editor will always have foibles associated with adding/renaming resources because it's dealing with such complex interdependencies. It makes sense to me that the editor won't remove things from resource.h because, as with the MFC classwizard (to use the old term from VC6) , it can't always get it right - and a missing line from resource.h has the ability to render an app totally uncompilable.
Duplicate Resource IDs are allowed when the underlying types of the two (or more) resources are different - so that could also be the reason why this functionality isn't already provided