Getting annoyed with intellisense

[Vodzurk]

Ok, for the love of god, please can somebody tell me why intellisense decides to stop working after the following (which compiles fineypoos)...

Direct3D::TextureLoader myTextureLoader;
// It works fine here
m_texture = myTextureLoader.FromFile(m_device, S"water.bmp");
// But not here!

It still allows stuff like System:: and String:: to popup the intellisense, but not my own classes!

m_texture = myTextureLoader::FromFile(m_device, S"water.bmp");

has the same effect too.

Grrrrrr! (thats my impression of that goblin thing at the end of the buffy credits ;) )

[DNA5122]

Visual C++ intellisense has always been pretty bad. It's like it can't find things beyond local files. And if theres things it can't find it just stops working all together. Thats the one thing Visual Basic has going for it. If intellisense doesn't work in VB it means you have a compile error and as soon as you fix it it starts working again.

[Andreas Masur]

You might want to take a look at Visual Assist (http://www.wholetomato.com/)... :cool:

[LuciWiz]

Well, I've beem posting on another forum about my troubles with Intellisense, but nobody answered (well, I got something about deleting the .ncb file, but that wasn't it).
What I actually reported was that it stoped working after I changed the location of my project (to another directory); any thoughts?

Anyway, I found Visual Assist to be the solution too :thumb:

[Vodzurk]

Thanks for the advice guys... good to know others experience this and its not my installation or anything.

An intermediate solution... i've just thrown the functions to the bottom of the class (like, yeah, g'wan and break that brace and semi-colon, i dare ya!).

I'll give that Visual Assist program a miss though... just blown this months salary on silly things (holiday + booze).