Where did the help go?
Author
I'm using Visual C++ 6 and DirectX 7 and Windows 95
Ok, you know when you write say:
lpdd7
and then with ->
lpdd7->
You should get a list of the functions and variables of lpdd7, right?
Well it doesn't work in my ddraw project. Whats wrong?????
Please help me (if you understand my problem =)
Btw, will it help downloading the latest sdk from microsoft?
(I've got cable so time isn't a matter =)
Edited by - ZomeonE on 1/9/00 10:38:44 AM
Edited by - ZomeonE on 1/9/00 10:56:39 AM
This may help, works with MFC type problems of the same nature:
In your project, make sure that you actually include the header files in your project for the object(s) you want automatic type info displayed for, not just inlcuded by way of an #include statement.
If you do this correctly you should see the appropriate header files in the "include" section of your files project, not as an "external dependecy" reference.
Note: Your project should compile successfully either way. This is only an IDE feature and has no bearing on whether your compiler "compiles" and your linker "links". Also, if your type info goes away out of the blue, try to do a scope resolution operator :: and see if it pulls up any information. If it doesn't, you might want to clean your project as it get's hosed every once in a while if you don't do precompiled headers correctly...
Just another bit pusher,
deadlinegrunt
(I see how the smiley face get's there now)
Edited by - deadlinegrunt on 1/9/00 1:00:03 PM
In your project, make sure that you actually include the header files in your project for the object(s) you want automatic type info displayed for, not just inlcuded by way of an #include statement.
If you do this correctly you should see the appropriate header files in the "include" section of your files project, not as an "external dependecy" reference.
Note: Your project should compile successfully either way. This is only an IDE feature and has no bearing on whether your compiler "compiles" and your linker "links". Also, if your type info goes away out of the blue, try to do a scope resolution operator :: and see if it pulls up any information. If it doesn't, you might want to clean your project as it get's hosed every once in a while if you don't do precompiled headers correctly...
Just another bit pusher,
deadlinegrunt
(I see how the smiley face get's there now)
Edited by - deadlinegrunt on 1/9/00 1:00:03 PM
I have encountered this problem before. I solved it by deleting the .ncb file. I don''t know if this will have any side effects though, but as far as I know MSVC will just rebuild the NCB file.
-Jey Kottalam
14 Year Old Computer Programmer
http://www.armageddongames.com
-Jey Kottalam
14 Year Old Computer Programmer
http://www.armageddongames.com
I had that problem, here is how to fix it (or at least how it worked for me):
Add all the DX7 includes you need the info for into your project, then the parameter completion should work. Then you can take them out of your project, and the parameters should still work.
-----------------------------
"And I write and I write and I don't believe it's gonna change today"
- From Yellow Ledbetter by Pearl Jam
http://www.crosswinds.net/~uselessknowledge
Add all the DX7 includes you need the info for into your project, then the parameter completion should work. Then you can take them out of your project, and the parameters should still work.
-----------------------------
"And I write and I write and I don't believe it's gonna change today"
- From Yellow Ledbetter by Pearl Jam
http://www.crosswinds.net/~uselessknowledge
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
