Native Development

[simon_hain]

I have to initialize all pointers with NULL.
That seems to be the reason for the whole mess. I will do that for all my materials and check back, but it seems to have resolved this issue.

There should be a big sign for java developers going c++ with stuff like that, placed conviniently above my monitor...

Thank you for your patience BGmot!
Let's see if that resolves everything

[BGmot]

I am afraid I was misunderstood.

I personally *do* initialize all my pointers with NULL or real values.

And I *do* expliciltely set them to NULL when objects they point to are deleted.

Some may argue that this does not make sense though... to me it is just cleaner code and checks for NULL often help.

[simon_hain · Accepted solution]

Well, i did not initialize pointers with 0, i assumed that unless i put an object there it would be null.
I should have thought about that, as i read about bool being able to have three values and int variables having a value on their own, but alas, i did not.

So, to conclude:
kids, initialize all pointers with NULL (or 0). Especially if you are a java developer that has a whole other concept of it.