Quote:Original post by lord_balron
The Objects have a variable containing their location in the vector so you can access it with.

As mentioned, this is a very bad idea.

Quote:
This is given to it with this code...

void Particle::AddChild(Object* Child){	Children.push_back(Child);	int i = 0;	//for (int i = 0; i < Children.size(); i++)	while (Children != Child)	{		Child->PositionInVector = i;		i++;	}	Child->Parent = this;}

So every time you add a child, you re-number all the previous children, even though their places haven't changed. Then, because of how your while condition works, you don't actually number the child that was just added (note that the commented-out approach would have worked). You also depend on operator== working properly for Objects. And why is a Particle allowed to have any kind of Object as a child, anyway?

Quote:
What problem I'm having is that when I go to release it with:

Place = Place - 1;Children.erase(Children.begin() + Place);

I get an error (through the visual studio realtime debugger), that my program is "Access violation reading location 0x00000000"

1) Have you tried verifying the value of Place?
2) After erasing an element like this, all the elements that followed it will get shifted down, and need to be renumbered. There's no code anywhere to do that.

I can't get this working, what is a better way to hold dynamic scene objects?