§ ¶Weird bug of the day
Today's bizarre bug: it seems that at least on my system, if I have any top-most windows on my desktop, hitting Windows+D twice in quick succession causes the top-most flag to spread to other top level windows. Thanks to this weird behavior, I now have Visual Studio, Firefox, a Command Prompt, and WinVi32 topmost and everything else I launch is getting dumped below them.
I don't generally run desktop adornment programs, so there aren't a lot of possible culprits here... I think it's basically either Windows 7 x64 or NVIDIA nView (which should be off).
Don't see it on my system. probably nView... I didn't even install it. The new NVIDIA drivers installer give you much more control over which components you want to install.
Username - 29 01 11 - 13:35
Something is seriously broken on my own Windows 7 machine w.r.t. window ordering. Alt+tab often changes the active window, and reorders the windows in the alt-tab popup, however the actual focus and z order is not affected. pressing it again twice will have the same effect.
I have yet to isolate this problem. The only 3rd party software that could seemingly cause it is VNC server, but that makes no sense.
David W - 29 01 11 - 16:44
Sorry for me being too lazy to look up the correct registry key and links, but I think you see the normal behaviour of Vista and Win7:
Raymond Chen describes in the oldnewthing that LRU-order is only used for the last 3 windows, after that they sort it alphabetically, because people's mind would not remember more than the 3 last windows. This is ridiculous of course and really reall stupid.
I turned off the new fancy alt+tab screen which I like and now have the same thing one sees if the explorer-process is killed: An ALT+TAB like in XP only with icons, not with previews.
Now I have my Z-order back.
An alternative could be that you learn alt+esc or something, maybe it preserves the z-order better
Christian - 29 01 11 - 21:15
I can reproduce the top-level Win-D problem on my Win7 laptop which has ATI graphics, so it's not NView (unless the same bug exists in two things).
I cannot reproduce it when remote desktop'd into my main Win7 machine (NVidia graphics but no NView, FWIW), so I suspect the bug is in, or triggered by, DWM (which isn't in use when I use RDP).
To repro on the laptop, I opened two windows, made one always-on-top (via an option in the app itself), hit Win-D twice, then opened a web browser and saw it was stuck behind both windows.
Leo Davidson (link) - 29 01 11 - 23:12
For what it's worth, I couldn't reproduce this.
Win 7 x64 & radeon graphics.
fmagreed2 - 30 01 11 - 02:04
Now that I'm no longer using RDP (and now using DWM), I can repro this on my desktop as well. (Both desktop and laptop are Win7 x64.)
At least right now, on the Desktop, it seems to only make on-top the window which was active when I pushed Win-D the first time. So if that window wasn't on-top but another was, both will be on-top afterwards, but the other windows are left as they were.
I suspect there's more to it than that as I don't think it was quite the same when I repro'd it before.
I've also repro'd it using two different programs as the on-top window, so it's probably not something peculiar any particular app is doing in its on-top/z-order handling.
Leo Davidson (link) - 30 01 11 - 21:11
I have the same bug, win 7 x64, Nvidia 240GT.
EO - 07 02 11 - 01:36
Please keep comments on-topic for this entry.
If you have unrelated comments about VirtualDub, the forum is a better place to post them.