MajinSephiroth
15-02-2007 22:55:48
I'm experiencing a bug which I am not sure on how to describe.
Basically, as soon as we define a physics world size, every pointer and variable becomes a const Ogre::Vector3 &min
The moment we comment out
mWorld->setWorldSize(Vector3(-500,-500,-500),Vector3(500,500,500));
everything returns to normal.
Where
OgreNewt::World *mWorld;
and
mWorld = new OgreNewt::World();
Has anyone ever experienced this issue before? We are using VS 7.1
leakingpear
16-02-2007 16:19:05
If you're not using the Ogre namespace you need to add Ogre:: to the front of the Vector3 constructors in the setWorldSize line. Other than that I can't see anything wrong.
MajinSephiroth
20-02-2007 22:23:52
That's why I'm not sure of what's going on.
We are using namespace Ogre, I even tried adding the Ogre:: to the Vector3's and still nothing.
walaber
21-02-2007 00:38:45
Basically, as soon as we define a physics world size, every pointer and variable becomes a...
what do you mean by this?
MajinSephiroth
21-02-2007 22:34:04
Well, a picture's worth a thousand words, so here's what I am refering to:
Pointers Working:
Pointers Not Working:
This is just a general way to show this bug, it happens with any pointer you try to access anywhere in the code below:
mWorld->setWorldSize(Vector3(-500,-500,-500),Vector3(500,500,500));
Don't get me wrong, the pointers still work properly, it's just that VS7.1 "loses track of them" or so to speak, which is annoying.
Game_Ender
22-02-2007 00:54:27
Well that one is only worth 5 words
: "Code completion has stopped working".
walaber
22-02-2007 07:50:35
if you change all of the "500" to "500.0f", does that help? I'm just curious.
MajinSephiroth
22-02-2007 20:08:53
Game_Ender: gee thanks
Walaber: tried that, no dice
walaber
22-02-2007 21:32:55
weird. I've noticed the autocomplete is much improved in MSVC++ 2005 (8.0), but still nowhere near as convenient as MSVC# 2005.
MajinSephiroth
23-02-2007 20:02:23
Well, it's not that the autocomplete does not function properly per se, it's almost as the information that it's being fed is completely changed after that line.
Allow me to demonstrate:
Before Commenting:
After Commenting:
What you see in the "after" is exactly how every variable, function, pointer gets treated by MVSC after that line.
OvermindDL1
23-02-2007 20:15:02
First of all, the intellisense in all VC versions kinda suck, if you have the money, fork it out for Visual Assist by Whole Tomato, well worth it if you code for a living (or a major hobby).
Second, the intellisense cache is probably just corrupt, either download (can't remember the exact name) the extension for VC that can flush by clicking the button it adds, or shutdown visual studio, delete the intellisense file for your project, and restart and let it rebuild. This is of course assuming your project actually compiles without warnings/errors in that file.
Scorch
01-03-2007 01:07:34
I use VC8 express at home. The Intellasence gives out on me several times per programming session and I just don't bother with it usually.
I use slickedit at work. You have to build your own tag files, but never has given up on me. It does a better job in the whole tag-lookup area. It also has a few other editor features that visual studio lacks.
http://www.slickedit.com/
I don't use it at home because its not free, and visual studio 8 express is.