|
November 21, 2006
WindowShade X 4.1.1
WindowShade X 4.1.1: Just a bugfix release aimed at fixing two bugs: when WindowShade X appears as active, registered, and everything, but does nothing (mostly happened on upgrade installations), and with "Press Command/Control Key Twice" action suddenly stopping working in a particular application. Speaking of the latter, for some reason it's referenced as DoubleTouch internally in the sources. Go figure... http://unsanity.net/windowshade-x-411.dmg (free upgrade)   Posted by slava at November 21, 2006 11:29 AMTrackback Pings: TrackBack URL for this entry: Related:
Comments
Well, initially these two bugs were fixed (and I was happy), but as soon as I restarted they were back. Posted by: F451 on November 21, 2006 12:26 PMAddendum: Safari windows are the only place, for me so far, that these features do not work: Press Command/Control Key Twice WSX Version 4.1.1 F451 - Sadly I'm getting some issues with Safari too. Looks like we haven't quite nailed the double-tap issue fully. Thanks for the heads up. Anyone else getting this? Posted by: Brian on November 21, 2006 3:48 PMBrian, Well, I got it back, but then I lost the use of Spotlight, as it would not drop-down. Then I used Tiger Cache Cleaner to cleanup my system, restarted, and all appears to be on track again with Safari doing as it should with WSX. Posted by: F451 on November 21, 2006 4:25 PMFollow-up: The Safari use of Press Command/Control Key Twice is only available for a time and then it becomes unavailable the longer I use Safari. Relaunching Safari brings the features back. Posted by: F451 on November 22, 2006 12:39 PMHi Brian, thanks much for your quick response to my e-mail to unsanity. After re-launching Safari, "Control Key Twice" came back to life, and is OK now - even without the upgrade to 4.1.1. Windowshad STILL doesn't work in Finder... Is this a known issue? R Posted by: Ryan Clark on December 1, 2006 1:26 PMSo what if it still "appears as active, registered, and everything, but does nothing" Any tips? I miss my shades Posted by: Luke Andrews on January 21, 2007 3:56 PMWindowShade isn't as compatible with Intel as it might seem. I just had to uninstall APE and WindowShade from my MacBook Pro. Our IT troubleshooter finally convinced me that he had narrowed down the root of my seemingly unconnected software issues with apps like Symantec AntiVirus and InDesign CS2 to APE and it seems he was right. As soon as I uninstalled WindowShade and APE everything worked perfectly. Too bad. I've always liked Windowshade, but not so much that I can put up with the fallout on my Intel-based MacBook. Posted by: Gary Ludwig on February 1, 2007 7:28 PMI am having a problem that appeared just after |