| Author |
 Topic  |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
 Posted - Jan 10 2004 : 1:28:45 PM
|
VA_X 1210:
1.) #include suggestion completely broken (doesn't suggest any header-file anymore)
2.) while typing "strcpy", VA always suggests StrCpy, even worse: when I type "strcpy(", it replaces my beloved "strcpy" with "StrCpy"... |
 |
|
|
Uniwares
Tomato Guru
Portugal
2321 Posts |
Posted - Jan 10 2004 : 1:51:47 PM
|
| Turn off "Repair Case". Doesnt work. |
 |
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jan 10 2004 : 2:51:55 PM
|
Okay, I'll try, but I don't think it'll fix it.
When I type strcpy, the Popup-Box appears and suggests several strcpy's, but not "mine"...
It's hard to explain, as if VA doesn't know "strcpy" from the C-Runtime Libraries!
/EDIT:
Okay, removed "Repair Case" and it works again! |
|
Edited by - WannabeeDeveloper on Jan 10 2004 2:53:13 PM |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jan 13 2004 : 4:40:00 PM
|
1) Build 1211 fixed the completion of #include.
2) If you are running VS.NET 2002, it might have been the Directories node in our options dialog. The fields were not getting populated correctly. Build 1211 have a fix for this as well.
Please try build 1211 and let us know if the strcpy problem persists, even with "Repair case" enabled. |
Whole Tomato Software, Inc. |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jan 14 2004 : 05:59:15 AM
|
Nope, as posted in the "Build 1211 available"-Thread:
Not fixed yet! |
|
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jan 14 2004 : 06:55:34 AM
|
We think their is something wrong with your include path. If you type #include <string.h>
, does the VA definition field display the path to C:\\Program Files\\Microsoft Visual Studio .NET\\Vc7\\include\\string.h?
There was a fix in 1211 for include paths in VS.NET 2002 and were hoping it would fix your problem as well. |
Whole Tomato Software, Inc. |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jan 14 2004 : 07:23:59 AM
|
Okay, let's see if we get this together...
I start typing:
When I press TAB now, it completes the "#include" but doesn't fill in <> or ""
When I manually enter <, it types <> automatically, but no list pops up! Not even after typing inside <>
after typing "#in", this comes up:
which was shown in VA .NET before, but not in VA_X.
selected the bottom-entry:
I have no idea which path it is showing there... How can I find out?
Hovering the Mouse over it doesn't show a ToolTip to show which File it is...
continue typing (#include <str>):
note that string.h doesn't even show up...
these are the include-paths in the VA_X Options:
...which looks okay.
C:\\Programme\\Microsoft Visual Studio .NET\\vc7\\ is my Install-Path for VS .NET 2002
C:\\Programme\\Microsoft SDK\\include\\ is the Platform SDK from February 2003 (newest one).
This behaviour is somewhat strange... because when I continue typing "strin", suddenly the Popup
changes and shows the desired string.h:
I don't even dare to tell you what happens when I press BACKSPACE in there:
Pressing Backspace once:
pressing Backspace several times:
|
|
Edited by - WannabeeDeveloper on Jan 14 2004 07:26:36 AM |
|
|
|
WannabeeDeveloper
Tomato Guru
Germany
775 Posts |
Posted - Jan 14 2004 : 07:37:18 AM
|
Ah, wait a second....
Somehow, the "Projects --> C/C++ Directories" were not showing "Win32", but "Custom" (although both Directory-Lists look absolutely the same). Changed it to "Win32" and now strcpy is correctly suggested and string.h shows up in #include-List.
Strange... |
|
|
|
| |
Topic |
|
Topic Locked
