wyBuild seems to start up in this state when launched from Explorer via file-association.
e.g., right now I'm looking at wyBuild window - mostly white, while it loads our project file. This takes something like a minute. While that happens, the wyBuild window is on top of this browser window (and all other windows). When it finally does load my project, it remains on-top, and refuses to go-under.
I noticed that when I first launched wyBuild without a project (or from a nearly blank project), that it did not take long, nor did it stay on top.
So my guess is that when it is loading from file-association (i.e. I double click on our .wyp file when wyBuild is NOT currently running) and the file is large (takes wyBuild long enough to open it), then it gets stuck on-top.
BTW, I almost reported as a bug or concern how long it takes wyBuild to load our projects. (I just clocked it at 53 seconds) on my good developer box (3.2GHz core 2 duo).
Also, if I launch wyBuild from file-association using a small .wyp, I do not see this problem. So it has be:
* wyBuild not currently running* launch from Explorer using file-association* .wyp file must be large enough to cause issue* doesn't matter if .wyp is loaded from network or local, just has to be large.
And nearly a min to load is annoying, if there is something you can be doing to eliminate this delay (lazy load some aspects, such as the list of files in the various version tabs)?
EDIT:* Test environments: Windows 7 x64 && Windows Server 2008 x64 (both fully up to date)
EDIT2:* I did test if wyBuild is already running properly, launched w/o a file or a small file, then do an explorer-launch of a large project, and found that this did not cause problems.
Perhaps the window's default characteristics are "force on top" and that is reset to normal at completion of initialization, but if loading takes too long somehow that piece of initialization fails?