I very often have new windows open behind existing windows. I don't want "always on top" or any of that type of nonsense. I just want new windows to open in front of existing windows. I tried changing ForegroundFlashCount and ForegroundLockTimeout, but to no avail. I currently have them set to 3 and 200,000 respectively.
Aa in having them Maximized and wanting to layer each one over as the OS minimizes the rear one into a sort of standby state. The first option you are playing with flashes the taskbar, the second one you are playing with decides how long that process stays in the foreground before the OS places it into a suspended state to lower CPU resources, unless there is activity happening in that window such as downloading, maintenance, malware scanning, which overrides the second setting.
The same as it has always been done in Windows. If you want to just click to bring up, Move cursor to Taskbar and then have the preview come up to choose the window for the app.
Last edited by bro67; 24 Sep 2017 at 15:44.
I've always thought that the normal behavior was for a newly opened window to open in front of all the other windows, so that you can see it without the additional step of bringing it to the front. Was I mistaken about this?
This as you've found seems to be a problem that's plagued some from at least Win 7.
See this- at least it's different to what you've tried, but it may be hard to find a solution.
Taskbar bug: switching to another window -will not appear at the front - Windows 10 Forums
Does it happen if you create a new user (just for test purposes)? If so it's a windows issue, if not it's a user profile issue.
@gregyurkon
Two things to try. First try the launch folder separate setting.....turn on if off, off if on. Toggle it to see if it that works. Should sign-off/on after tweak.
Second, re-apply your current theme. Probably would need to set a default theme, then set back to the one you want.
When you open a new window, it will always come up and cause another window to go into a background process until it goes into a hibernation sleep if written into the code and release memory. The worse thing that you want is a program in the foreground as another and cause a memory leak to eat up all available memory.
Dealt with that issue way too much with idiots using the wrong way of creating programs and a Intranet website for a state government and no one that had the title of "IT/LAN" had a freaking clue, even those who went to school and use Mac OS, but did not understand that when someone working on that computer is in the middle of something and cannot save it because of what they are doing.
You end up idiot with the title of IT walks up and shuts down everything without waiting, is when you tell them that they are not to touch your workstation until you are there and have saved your work.
Not once did I ever get wrote up, nor pulled into a manager's office, since they knew that I was in the right and told the idiots from the IT group to wait until the workers are done with what they are doing. That was because your manager had gotten tired of losing work and dealing with hearing employees scream WTF when they come back after lunch or had to go do something and the work that was needed by another unit is gone.
Quote
