RGB World Forums

indeed it is resolved thank goodness

I always find it a good practice resetting prefs to defaults and re-configuring when a new WindowMizer versions comes along...did you try going down this route?

Hm...having v.4.4 installed on my daily driver while at the same time being unable to roll back due to the nature of one of the bugs I can't say that i don't feel a bit dissapointed by the time that this is taking for patching up, let alone the lack of updates... ...just a reminder; we're now within...

I noted that every time I start a program now, I get a notification that "Windowmizer is ready in: <program name>" I do not recall this behavior before and it's kind of annoying. In the prior version, I got a single notification on WM startup telling me WM was ready. In order for such notifications...

Thanks for the update, too bad it didn't go as planned. Hope you come up with a proper solution in due time, however I stand by your decision in releasing a patch first as this is getting pretty annoying (single-dock-click-action) ...

Seeing that the weekend is now already in the past, I just thought I'd ask how that update is shaping up...

Bummer...so my favorite option was to windowshade with the dock remaining uncluttered and now you're taking this off completely at v.4.5? Is there no way to keep the functionality (i.e. windowshade result w/ uncluttered dock) but change the underlying mechanism to get there?

I've also experienced much drama upon updating and the patch didn't appear to do much...until i rebooted (there goes the uptime) by which time it did successfully proceed to show the WM UI... One other thing I noticed though is that after the update I now have to click twice or sometimes more times ...