Recently I developed a program that should run a process and make it foreground. Everything was ok except for one case: when there's a full-screen application active currently, the one that due to non-captioned styles and screen dimensions hides tasbar and fills all the area of the screen. In this case in Windows 7 the running applications seems to not appearing over this full-screen app at all.
At first place I thought that it's something introduced after XP, I should live with. But today I had a chance to check this on two Windows 7 Home Premium, but they were different in "bit" variation. And it appears that Windows 7 64 bit allows newly application to appear over currently active full-scrren app, while 32-bit version does not. Both versions of Windows have the same language and the same UAC setting, both have Classic interfaced on and Aero Off.
I may be wrong about the cause of this behavior so if anyone can check it and want to, here's the conditions:
Run a full-screen application, for example Google Chrome with full-screen menu activated
Create simple application that does CreateProcess with all default settings (structures filled with zeros). Make it to run the process after button press, but let it delay it enough for you to switch to the full-screen app with Alt-Tab or taskbar.
Wait for something to appear. In my case I saw the newly executed app in case of Windows 7 64 bit and nothing in case of Windows 7 32 bit.
The question in the subject is about which way is an unexpected way, so should this newly app appear or full-screen application have some special priority in Windows 7 so it's the 64 bit version that does something bad. Or my conclusion about 64 bit/32 bit difference is wrong?
Sorry, this is not my first post about full-screen applications, but things are changing every day.
Max