Something wrong with device->closeDevice or device->ru

Dark Saint · Post by **Dark Saint** » Sat Oct 06, 2007 4:52 pm

Hi. Maybe it is a bug. When i trying to run the example 05 from irrlicht SDK and press button "Quit" the program cannot finishing. The main window is destroyed by console window is still alive. Why?

hybrid · Post by **hybrid** » Sun Oct 07, 2007 11:26 am

The quit message is not properly handled. Niko will fix this issue anytime soon.

Spintz · Post by **Spintz** » Thu Oct 11, 2007 2:35 am

GnarlyHotep · Post by **GnarlyHotep** » Thu Oct 11, 2007 5:09 pm

I just stumbled across this as well, I believe. The problem appears to be that the window is destroyed in closeDevice() before the message is posted/retrieved. Changing

Code: Select all

 DestroyWindow(HWnd);
 PostQuitMessage(0);
 MSG msg;
 GetMessage(&msg, NULL, WM_QUIT, WM_QUIT);

to

Code: Select all

 PostQuitMessage(0);
 MSG msg;
 GetMessage(&msg, NULL, WM_QUIT, WM_QUIT);
 DestroyWindow(HWnd);

fixes the process failing to terminate (although I don't understand what the PostQuitMesage / GetMessage are doing here).

Spintz · Post by **Spintz** » Fri Oct 12, 2007 1:12 am

Spintz · Post by **Spintz** » Fri Oct 12, 2007 1:42 am

hybrid · Post by **hybrid** » Fri Oct 12, 2007 8:15 am

If this change does not fix the closeDevice/createDevice problem what is it for? I thought that it is for exactly this purpose!?

Spintz · Post by **Spintz** » Sat Oct 13, 2007 9:52 pm

hybrid · Post by **hybrid** » Sun Oct 14, 2007 3:28 pm

Not the recent change, the one I've added in 1007 or so. What is it good for? I thought that it would avoid the problems with wrongly received quit messages.

Spintz · Post by **Spintz** » Mon Oct 15, 2007 1:24 am

hybrid · Post by **hybrid** » Mon Oct 15, 2007 8:37 am

Ah, ok, then it's like I thought. Thanks.

Spintz · Post by **Spintz** » Mon Oct 15, 2007 4:58 pm

mnunesvsc · Post by **mnunesvsc** » Mon Oct 15, 2007 9:20 pm

all this means the recent releases ( 1.3.1, 1.4 ) are still bugged, and we cannot drop the devices until these issues are fixed ?

hybrid · Post by **hybrid** » Mon Oct 15, 2007 10:36 pm

You can drop the devices, but creation of a second device might be a problem. These problems will be fixed before the final 1.4 release.

Spintz, is there a way to check if DestroyWindow was already called on a HWND? That would be the best way to fix run(), because it would also fix cases where the user called DestroyWindow on the handle.

Spintz · Post by **Spintz** » Tue Oct 16, 2007 11:49 am