One way I still see windows getting lost is (with all taskbar items visible) to attempt to use the close button in the taskbar thumbnail to kill an application that isn't on the current desktop.

With many applications, the button does nothing - VirtualBox springs to mind - however some applications will close and when launched again have an off-screen window - Google Chrome being one example. Also; it's 100% repeatable.

I _finally_ seem to have a way to work around the issue.

I tend to be impatient, so while something like Visual Studio is loading a large project I will change to the desktop with mail to check mail, flickr across to the desktop with the browser to check gmail, etc. etc.

I have all the common applications I used assigned to particular desktops (I use 6 in a grid).

I think the combination of that setup and my behaviour results in dexpot losing track of the desktop an app's window should be on (can happen to a subset of open windows for an app), and the window ends up without a valid desktop.

If I restrain myself from changing desktops while an app is performing a long operation (like starting up, but not just limited to that), things are better, but not perfect.

With the following setup I just got through a whole day without losing a window (having it disappear down to below the bottom right of the screen, or into the nether regions of being visible but not selectable). Generally I'm restarting apps or Dexpot probably 6 or more times a day without this change.

Under Settings -> Plugins and Extras, in 'Behaviour of windows on other desktops' set 'When activating a window on another desktop' to 'Do nothing'.

HTH

I've been toying around with some options and doing the following eliminates the issue of the Steam chat window disappearing: Set the chat window to be copied to All Desktops.
It seems that the issue lies in hiding the window and retrieving it back, that it somehow gets moved elsewhere....

I'm having the same issue with Steam. Logfile at http://www.kutaghs.co.cc/dexpot.log
You're looking for the window handle that ends at '- Chat' (Shotor - Chat, Keffertjuh - Chat and so on). Gotta look at around 01:10-ish for example...

A large log is fine, if you can tell me when the problem occurred and which window was affected.

I still lose windows. Do you need a log that just has the problem, or can you extract the necessary info from a large log (I'm a developer who runs 6 desktops and two monitors - so there's a lot going on in my logs).

dkarr wrote:I am unable to make my test case fail. I'd say that bug is taken care of.

Finally...

Do you believe this fix will have any impact on the other two problems I've seen

No connection. I'm not even sure that this particular bug accounts for all the cases of lost windows that have been reported. Additional feedback from others who have posted in this thread is welcome.

I am unable to make my test case fail. I'd say that bug is taken care of.

Do you believe this fix will have any impact on the other two problems I've seen:
* Process Explorer randomly unminimizing itself on desktop switches
* Some windows of "busy" applications get duplicated to other desktops on desktop switches

These two issues are harder to repeat, but I've seen them consistently with earlier releases.

Found and fixed a race condition. Please tell me that was it...

If not, new log.

Here's the log file.

Could you repeat your "test case" again with this version and upload a new log file? Thanks!

Ok, it's wk3 now, and I repeated the test case again. Here's the log.

I've done the same and it definitely shows up as "Build 1805-wk3" for me.

I just verified that the dexpot.exe attached to that previous note with the label "1805-wk3" is reporting a build number of "1805-wk2+ppp". I've done this twice now, with the same result. I've copied the executable over the existing "dexpot.exe" in the Dexpot distribution.

Thanks... but there don't appear to be any runs of the new wk3 build in that log file?

Here it is.

I might have mentioned this before, but what I need in terms of feedback is a LOG FILE.

With this build, my "load test" was able to cause windows to disappear very quickly, but that's not normal usage.

My "load test" has my 3x3 grid, and I start my messaging app with two windows in desktop 8. I have Alt-Win with Arrow-Left and Arrow-Right bound to switch to desktops left and right respectively. While in desktop 8, I hold down Alt and Win and then repeatedly bang on the left and right arrow keys for several seconds.

This test has never failed to lose one of the two messaging app windows. In this particular instance of the test, I had 3 windows on the messaging app (a search window). After a couple of seconds running the test, the contacts list and search window went away, leaving just the message window.

I'll continue to use this build to see if I lose windows in more "normal" usage. I likely won't have feedback on that until tomorrow sometime.

Thanks. I'll test this and get back to you.