Visual Studio Pointer Help..
-
I don't know what the proper terminology for it but I am trying to understand why the little popup window that you get when you are dealing with pointers or strctures, sometimes works and sometimes doesn't. Say you have a setup like this: struct MyStruct { int iData; } MyStruct mystruct; then when you type mystruct. <- here you will get the nice little pop up window.. Anyone knows why it doesn't work sometimes and why it does work?? Help please.. I like that little pop up.. I am using VC6.0 with service pack 5. I am specially having hard time with double pointers and for my first pointers I get that nice little pop up but not for the second one... :confused::confused::confused::confused:
-
I don't know what the proper terminology for it but I am trying to understand why the little popup window that you get when you are dealing with pointers or strctures, sometimes works and sometimes doesn't. Say you have a setup like this: struct MyStruct { int iData; } MyStruct mystruct; then when you type mystruct. <- here you will get the nice little pop up window.. Anyone knows why it doesn't work sometimes and why it does work?? Help please.. I like that little pop up.. I am using VC6.0 with service pack 5. I am specially having hard time with double pointers and for my first pointers I get that nice little pop up but not for the second one... :confused::confused::confused::confused:
This intellisense problem is a well known bug in VS6.0+ - think - and this is a guess only - it has something to do with includes. Not sure. Michael Mogensen.
-
I don't know what the proper terminology for it but I am trying to understand why the little popup window that you get when you are dealing with pointers or strctures, sometimes works and sometimes doesn't. Say you have a setup like this: struct MyStruct { int iData; } MyStruct mystruct; then when you type mystruct. <- here you will get the nice little pop up window.. Anyone knows why it doesn't work sometimes and why it does work?? Help please.. I like that little pop up.. I am using VC6.0 with service pack 5. I am specially having hard time with double pointers and for my first pointers I get that nice little pop up but not for the second one... :confused::confused::confused::confused:
Some times it is caused by an syntax error occuring before the current point. Some times the information is just not available yet (try recompile). Trust in the code Luke. Yea right!
-
This intellisense problem is a well known bug in VS6.0+ - think - and this is a guess only - it has something to do with includes. Not sure. Michael Mogensen.
I don't know if this was the case in VS6 (since I haven't used it in a while), but I have noticed that VS.Net refuses to give the popup if you have a syntax issue preceding the code you are currently typing. I wouldn't really call that a bug though. Now that I've noticed that it happens, when the box doesn't popup I start looking for a missing brace or semi-colon, etc. Kind of helpful in a way. I know it doesn't really help you with your problem, but just something to look out for. --Dean
-
This intellisense problem is a well known bug in VS6.0+ - think - and this is a guess only - it has something to do with includes. Not sure. Michael Mogensen.
Thanks for the info. I didn't know it was called 'intellisense'. This is not an article for VC6.0 but deleting .ncb file helped! :laugh: Thanks for your input! Keb. http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vsintro7/html/vcovrwhenintellisenseisunavailable.asp[^]
-
I don't know if this was the case in VS6 (since I haven't used it in a while), but I have noticed that VS.Net refuses to give the popup if you have a syntax issue preceding the code you are currently typing. I wouldn't really call that a bug though. Now that I've noticed that it happens, when the box doesn't popup I start looking for a missing brace or semi-colon, etc. Kind of helpful in a way. I know it doesn't really help you with your problem, but just something to look out for. --Dean
You are correct. This is what happens with VS6, too. Syntax errors will kill Intellisense in a hurry!