As far as I know there isn't much you can do when you are using fullscreen.
The minimized fullscreenapp indeed pauses until you click it again. If you want to maximise it by code, then you might need a separate Thread or process that is controlling the state of the main window. This might be a separate EXE that is running in a window, make it invisible by windowHide, if you want. I would however suggest to run the network handler in such a seperate window and then communicate between network handler window and fullscreen window over the clipboard, or over tcp or so. It makes things slower, but at least it would solve the frozen-by-minimize problem.
You'd need to identify the HWND etc. somehow, so the 2 Apps will be able to determine their counterparts HWND in order to communicate.
A further solution is to use a fake fullscreen resolution, but windows makes that rather hard IMHO, because it usually doesn't allow a window to use the entire Screen: max size is the desktop minus Window Frames and start bar. Possible workaround: use a msie fullscreen page as a black background. (need to get rid off the blitz window frames here too, using some API calls) But then again, who knows if those msie fullscreens are still supported tomorrow. Maybe some of the windows specialists have a better idea.
|
