October 21, 2003
Halo (No, Not The Game)

 WindowShade X 3.1b4 (release is available)

  • Once again improved shadows handling under Panther.
  • Fixed a bug with live shadow preview not being shown in the WSX Preference Pane.
  • Fixed an issue with WindowShade X Preference Pane name being shown as com.unsanity.windowshadex in System Preferences (Mac OS X 10.2).

We're close to the release, I hope!

Digg This!

 Posted by slava at October 21, 2003 06:06 AM

Trackback Pings:

TrackBack URL for this entry:
http://www.unsanity.org/mt-tb.cgi/178.




Related:
Comments

slava, don't you sleep? you're everywhere i go these days. anyway, is WindowShade X NOT working in 7B85? i installed 3.1B4 and logged out with no luck. Do I need a different version of APE?

Posted by: Kenneth Clark on October 24, 2003 6:33 PM

I've been entirely unable to get WindowShade X 3.1b4 to activate on a window titlebar under a 10.3 clean install. Keyboard modifiers, etc, all seems to work fine, just no double-click, etc in the titlebar.

Posted by: Shawn on October 26, 2003 5:43 PM

I had similar problems. Then I uninstalled all haxies and reinstalled them again making sure I was using the absolute latest from Slava. Now everything works. You might want to try this...

-mono

Posted by: monoclast on October 27, 2003 10:17 AM

Mono,

Thanks. That took care of it.

--ken

Posted by: Kenneth Clark on October 27, 2003 10:39 AM

Installed WSX 3.1b4 on retail Panther last night; so far, excellent. I was especially pleased to see the addition of Command-double-tap and Control-double-tap (the former of which I sorely missed from whatever shareware did that under Legacy Mac OS), but have found that I am really in need of control over the repeat rate at which it is engaged; i.e., I have a five button input device, set for Click, Command-Click, Control-Click, Option-Click, plus chording variations, and my work has me constantly Command-Clicking (e.g., for multiple selections) as well as Control-Clicking in certain applications, and I keep finding myself inadvertently collapsing or minimizing the window I'm working in. Very discombobulating.

Further, I have always had WSX 'Control-Double-Click' set to 'Make Window Transparent', but I now find that my Control-Click button, which used to set the transparency, now executes a minimization, instead. Yes, if I instead hold the Control key down on the keyboard while Double-Clciking, it behaves as expected.

Sure, I could slow down my work to avoid all of this, and, of course I could turn those new features off, but what fun is that? BTW, I did try adjusting the Key Repeat Rate under 'Mouse & Keyboard' PP, but it had no effect.

Would it be too much to ask for a (much) shorter tap-delay control so I can click as fast as desired when I'm working without tripping WS? Alternatively, is there a way to allow for custom selection of the trip key, so I could choose another that would be less likely to interfere?

Cheers

Frederico
(registered user)

Posted by: Frederico on October 27, 2003 8:53 PM

Whoops! Quick follow-up: I realized after reading my post that I was looking in the wrong place to affect the repeat rate; indeed, after changing the 'Double-Click Speed' setting under the Mouse tab, I was able to alter WSX behavior. Unfortunately, I'd already had that set to one notch below the fastest rate, and cranking it up to the highest setting was just a bit too much when I went back to editing text. Besides, I can still Command-Click too fast when making multiple selections in lists and trip WS.

It also had no effect on Control-Double-Click in title bar interference between settings.

As I think about the problems you would probably be facing in dealing with all of this, I'm beginning to suspect that I'm going to have to rearrange my desired activation settings to avoid some of these problems, but I still don't see how I can avoid the interferences when working within an application without disabling the new features altogether. I guess it's also likely in part the fault of Kensington software sending keystroke emulations in a way you didn't predict.

Posted by: Frederico on October 27, 2003 9:15 PM

installed the version above on my fresh 10.3 (7B85) and my most used feature, the double click windoshade didn't work. double 'apple' did work fine. hmmm. waiting.
=)

Posted by: #U on October 28, 2003 9:34 AM
Post a comment




Remember Me?

(you may use HTML tags for style)