szWindowName doesn't actually correctly set the window name?

by **Kzinti** » Sep 21, 2004 @ 9:31pm

No wonder I couldnt reproduce it, I was always putting my breakpoints in Game::OnSuspend().

Oh well. So now you have your fix =)

by **fast_rx** » Sep 26, 2004 @ 4:49pm

by **Kzinti** » Sep 26, 2004 @ 6:11pm

You don't want to do a FindWindow() with a window name, because this can indeed hang your app. This is exactly what you are getting.

I don't remember the details, but I think FindWindow() has to ask the existing window for its name by sending a WM_GETTEXT or something like that. This request can hang or stall for a long time.

by **fast_rx** » Sep 26, 2004 @ 6:49pm

That makes sense that another app may not be responding to the WM_GETTEXT request.

But, I don't see where PF is setting a class name, so what should you do to make it work?

And lastly, I was not using the mutex to determine when I should even be looking for the existing window. I suppose that is a safer way to do things, so that is added now. That will probably eliminate 99/100th of the problems.

by **Kzinti** » Sep 26, 2004 @ 6:55pm

by **fast_rx** » Sep 26, 2004 @ 7:29pm

szWindowName doesn't actually correctly set the window name?

Sort

Forum Description

Moderators:

Forum permissions