Thread: static variables and includes?

Most likely, the compiler doesn't know what the type vglTex is - you need to include the appropriate header file for that class.

--
Mats

i wanna define that object in vurtialGL.cpp and the class is defined in virtualGL.h
i dont include that file, because it is automaticly included isnt it?

well you see the source code i uploaded lately (..._demo3.zip)
what is it that i'm doing wrong? i think i might mis understood the usage of header files as well as several other mistakes... tell me please

No, there are no "automatically included" header files - anywhere.

--
Mats

The best thing to do is break classes into their own source files/headers so you can freely include those headers anywhere.

Includes are not complicated. You must simply include a file that contains a declaration of definition of what you're trying to use.
So make a vglTex.cpp file to contain the implementation. The source file should include vglTex.h, which contains the class definition, and all files that uses the class vglTex should also include vglTex.h.

dont know what i am doing wrong but it sure is my fault: i mean, i'm not very sure about all this. this works well, but as soon as i need classes, everything stops working well...

sample.cpp

Code:

#include <string>
#include "SDL/SDL.h"
#include "VGL-Inc/VirtualGL.h"
#include "VGL-Inc/Matrix.h"
#include "VGL-Inc/Utility.h"

virtualGL.cpp

Code:

#include <string>
#include <time.h>
#include "SDL/SDL.h"
#include "Matrix.h"
#include "Utility.h"

virtualGL.h

Code:

#include "SDL/SDL.h"
#include "Utility.h"

matrix.cpp

Code:

#include "VirtualGL.h"

matrix.h

Code:

//

utility.cpp

Code:

#include "SDL/SDL.h"

utility.h

Code:

//nothing included here

To rule out circular dependencies, you can try to break it out into its own source file/header as I mentioned.
I don't know where the class is used (and I believe it's defined in VirtualGL.h).

Split the class into its own files.
If you include the correct header and it still isn't working, then either your compiler is broken (unlikely) or you have circular dependencies - ie file A includes file B and file B includes file A.
Plus if you split it, it will much easier to debug what it isn't working if it's not working.

This is very bad programming. Do not use global variables and using a class to set an active global pointer is just another bad programming step.
Objects are self-contained. They do all the necessary work to function and expose interfaces for the programmer to work with them. There shouldn't be a SetActive function to set a global pointer to this class there.

Each function that works with such a class should instead take an argument to a vglTexture object, and not use a global "active" pointer.

And I stressed this before, implement the functions in the source file, not the header.

By doing something like "ActiveTexture = SomeTexture;"

Most graphics environments have a "Graphics Context", which is some sort of object/structure that contains "everything current" (or active to use your term). There are calls to "SetActiveXXXX", where XXX may be texture, pen/brush, etc, etc.

--
Mats