[SOLVED]Two irrlicht devies - problems

[vins]

I'm creating two irrlicht devices. But when I delete the second device the first one's run() returns false as if it wants to be deleted.
I can't understand why this happens. Aren't they two different instances?
Also when used in GUI framework the messages that closeDevice sends, tells the framework to close the application:

Code: Select all

void CIrrDeviceWin32::closeDevice()
{
	MSG msg;
	PeekMessage(&msg, NULL, WM_QUIT, WM_QUIT, PM_REMOVE);
	PostQuitMessage(0);
	PeekMessage(&msg, NULL, WM_QUIT, WM_QUIT, PM_REMOVE);
	DestroyWindow(HWnd);
	Close=true;
}

Currently I delete the device like : delete device;
Is that bad? The window handle is being deleted by the GUI framework and I don't use the device after that so it should not be a problem, right?

Thanks.

[CuteAlien]

Usually you should run closeDevice() first before deleting the device. And it shouldn't really quit gui-framworks as the quit message is consumed immediately afterward. I 'm not sure why it is done the way it is done. Looks like something grown from experiences, I think formerly people needed another run() after the closeDevice() sometimes. You might want to call also clearSystemMessages () before or after the closeDevice() to make sure no events for a closed device get passed on to a new device which you create afterwards.

But I suspect you already tried that stuff... can you paste a quick example we can use for testing?

Another thing - don't use delete in Irrlicht for objects created with a create function. Use device->drop() instead and set the pointer afterward to 0. It's just safer, although in this case it probably makes no difference here.

[vins]

...people needed another run() after the closeDevice() sometimes...

Thanks alot man! I haven't tried that. I just added a call to run() after closeDevice() and it now works fine