I was going to keep on testing a little while longer, to provide more info, but after reading the Release Candidate announcement about error reporting, I thought that I had to post it now. So, the problem is random-looking unintentional DesktopWorkArea changes. That means, which actions in my PC trigger an automatic DWA change.
A !refreshApp bang is required to reset the DWA. I keep following this since the late r800 - early r900 builds.
I open a .torrent file with uTorrent (not running until then) or when I try to maximize it through tray
I open skype
I send this !bang: [!RainmeterPluginBang "MeasureBin EmptyBin"] in RecycleManager.dll
These are the most common actions that trigger the DWA change. I suspect that, one way or another, Windows and the other programs listed mess with desktop resolution when loaded, and that's way the DWA is changed.
I hope I have gathered enough information for this.
Inactive, due to life changes. Send me a PM for any question.
I noticed a WorkArea reset when starting a fullscreen application (like a game). I don't think that's unusual considering the application wants to run on the whole screen and not just a part of it.
That's true, it also happens to me. But that's not the case here. The programs producing the error don't even start in maximized mode. VLC opens a pretty big window pretty much the size of the screen, however.
Inactive, due to life changes. Send me a PM for any question.
As far as anyone is concerned (or happened to have the same problems as me), I have concluded almost definitely that most of the DWA problems were caused by the Objectdock I was also using, with the option to "hide the taskbar" enabled. Eventhough it work well (it hid the taskbar, and the DWA was rendering correctly) the above actions triggered something that didn't like the DWA+Objectdock cooperation. So, when I stop using Objectdock and went back to Windows taskbar, the above problems don't appear any more.
Just my 2 cents.
Inactive, due to life changes. Send me a PM for any question.
