| T O P I C R E V I E W |
| Cuong |
Posted - May 05 2006 : 11:28:55 PM
In my VC++ projects (VS2005), all new resource IDs (that I create) are always in black color. I try to delete *.ncb and I also close/open VC++ projects but the resource IDs are not colored. This problem does not appear in VS2003.
I am using the lastest version of VAX in VS2003, VS2005, WinXP SP2. |
| 8 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - May 18 2006 : 2:40:50 PM
do you have the ResOrg plugin installed? any other plugin's installed?
which IDE and version of VA are you using? |
| TomKnox |
Posted - May 18 2006 : 04:44:20 AM
I have the same problem. If I change the DialogID in the ResourceEditor, the new id isn't recognized until i open the resource.h and manually reparse the file. I think this is not an ideal solution, because every time i open the resource itself, the ide wants to close the resource.h. In the configuration dialog, i have activated the switch Watch for external modified files, but that doesn't change anything. |
| feline |
Posted - May 10 2006 : 3:20:01 PM
i don't understand your question about IDE parsing settings. there is:
VA Options -> Text Editor -> listboxes -> get content from default intellisense
and also under the VA menu you can select to manually reparse the current file, which is what i was referring to.
it sounds like these resource ID's not being coloured was a symptom of the conflict between VA and ResOrg. i am glad this is now working for you. |
| Cuong |
Posted - May 08 2006 : 8:58:57 PM
I did not change any setting related to IDE's parsing in VS2005. Is there any way to check if this feature is turned on or off?
At this time I have also problem with ResOrg add-in. It conflicts with VAX so VS2005 always hang at startup. I follows rhummer's advice. That is to re-install VAX and ResOrg by reverse order. This is a very very good solution. After uninstalling/installing (ResOrg first, VAX second), both VAX and ResOrg run properly without any conflict in VS2005. Futhermore, this also resolve my problem about recognizing new resource IDs. VAX now recognizes all resource IDs that I created new. I do not know why???
|
| feline |
Posted - May 08 2006 : 3:11:12 PM
odd. using VA 1445 and a C++ MFC project i cannot reproduce this problem. i added a new entry to the string table in both IDE's. in both cases after closing and reloading the project, but keeping the IDE open the new string ID was coloured correctly, but was underlined as a mistyped symbol.
after closing and reloading the IDE's it was coloured correctly, and there was no underlining.
i did not open resource.h at any point in this test, let alone manually reparse it.
the IDE's parsing is enabled in VS2005, have you done anything to stop it in your projects? this could be a factor.
are you seeing this problem with entries in the string table? or only with other types of resource ID? |
| Cuong |
Posted - May 06 2006 : 8:15:36 PM
@feline:
resource IDs include the string IDs in string table, the dialog IDs (e.g IDD_MYDIALOG), control IDs (e.g IDC_MYCONTROL) ... In VS2005, VAX does not recognize any new resource IDs I created. VAX only recognizes resources IDs that MFC created (e.g AFX_IDS_APP_TITLE ...). In VS2003, VAX recognizes new resource IDs after I close/open projects.
@rhummer:
Yes, after I let VAX to reparse resource.h, VAX recognize all resource IDs and they are colored. But if I create new another resource ID, VAX does not recognize this ID. Does I have to tell VAX reparse resource.h each time I create new resource IDs? I see that is not a good solution. Why VAX does not reparse automatically resource.h at startup?
**************************************
VA_X.dll file version 10.2.1445.0 built 2006.04.12
Licensed to:
VA X: [hidden email address] (1-user license) Support ends 2006.11.12
VA.NET 7.1:
VAOpsWin.dll version 1.3.2.4
VATE.dll version 1.0.4.15
DevEnv.exe version 8.0.50727.42
msenv.dll version 8.0.50727.42
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.2900.2180
WindowsNT 5.1 Build 2600 Service Pack 2
Single processor
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\PlatformSDK\\include;
C:\\Program Files\\Microsoft Visual Studio 8\\SDK\\v2.0\\include;
C:\\Program Files\\BCGSoft\\BCGControlBarPro\\BCGCBPro;
Library Includes:
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio 8\\VC\\crt\\src;
Other Includes:
|
| rhummer |
Posted - May 06 2006 : 6:14:08 PM
Feline, yes they are similar to a string table.
A work around is to open the resource.h file and tell VA X to reparce the file.
|
| feline |
Posted - May 06 2006 : 5:11:40 PM
assuming i do not know what a resource ID is, or how to create one, can you tell me what to do?
are these any relation to the ID's used to load strings from the string table? if these are an example of resource ID's then do you have this problem with ID's from a string table?
your comment about all new ones being unrecognised suggests that old ID's are coloured correctly. if this is so were the old ID's created in VS2003?
which version of VA are you using? given we have regular beta releases different people can have different definitions of "latest" version  |
