September 18, 2003
WindowShade X 3.0.1

Down to the details:


  • New actions to assign minimizations for: Command Key Pressed Twice and Control Key Pressed Twice allowing you to shade windows with your keyboard - my new favorite!
  • Window titles for Minimized-In-Place windows are now displayed below the MIP window if they would obscure the menu bar or go off the top screen edge.
  • Much better handling of smaller windows for minimizations (DragThing docks, for example).
  • Minimize-In-Place auto-alignment function now respects the Dock position and bounds.
  • Minimize-In-Place windows are being auto re-arranged when you expand one of the minimized windows.
  • Fixed a bug with Canvas™ 9 not being properly shading windows with WindowShade X.
  • Fixed an issue with QuarkXPress 6 disabling its menus if you Minimize-In-Place one of its document windows.
  • Fixed a bug with iChat still showing tooltips if the Buddy List window is minimized-in-place.
  • Fixed a bug with MYOB AccountEdge rendering tab controls inoperational when Control Center window is minimized-in-place.
  • Fixed a bug with iCab crashing if you click it's Dock icon when its window is MIPped.
  • Fixed a bug with drawer window reappearing on minimized windows if you have hidden and shown back the app with the minimized windows (Cocoa only).
  • Fixed an issue causing Classic Window Management by Robb Timlin not work in the Carbon applications.
  • Fixed a bug causing some Java applications to crash when expanding a minimized window (IntelliJ IDEA).
  • Fixed an issue with the Help button not working in the Preference Pane.

more info or download =)

Digg This!

 Posted by slava at September 18, 2003 10:10 AM

Trackback Pings:

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




Related:
Comments

Found a bug. With the auto-rearrange on, if you open, say, 5 finder windows to the "home" folder and then minimize them all, they stack on top of each other.

Posted by: pope52 on September 18, 2003 10:24 AM

On a fun note, however, they make an increasingly large shadow.... Minimizing 20 or so of them makes what appears to be a black hole in the top left of my screen.

Posted by: pope52 on September 18, 2003 10:25 AM

>On a fun note, however, they make an increasingly large shadow....
>Minimizing 20 or so of them makes what appears to be a black hole in
>the top left of my screen.

That's a problem with Apple's implementation of shadows. Shadows can be added to each other. In real life, a shadow is a shadow, and there's no such thing as a shadow inside a shadow (if there's only one light source). In Mac OS X, if there are two shadows on top of each other, there actually are two shadows, so it's darker.

Posted by: LKM on September 18, 2003 11:44 AM

my problem with v3.0.1

the auto-rearrange fix is nice, but...

i'd like the ability to pull MIP windows "out of the re-arrange queue".

what i mean is that i MIP a few windows, and then i want to pull a window out of the line and put in somewhere else on the screen. but if i do so, and then MIP or un-MIP a window, that window i've put somewhere else gets put back in the re-arrange line.

hopefully this makes sense. to try to explain again...

i want to have most of my MIP windows auto-rearranged, but also have the ability to manually put a MIP window elsewhere on the screen AND HAVE IT STAY THERE.

Posted by: petey on September 18, 2003 12:14 PM

another v3.0.1 problem:

this time with the 'dock awareness' and 'auto-rearrange'

i have my dock on the right side of the screen. i want my MIP windows to auto-rearrange on the right side.

i expected the MIP windows to line up to the left of the dock. instead they try to crowd into the small bit of free space to the top of the dock.

Posted by: petey on September 18, 2003 12:22 PM

to continue...

only when they've filled up that little bit of free space at the top of the dock do they start lining up to the left of the dock.

Posted by: petey on September 18, 2003 12:23 PM

Major problems for me when I installed 3.0.1 update. Could not log back in Finder and/or Dock would cause machine to lock. I installed for all users on machine. Only way out was to boot into OS 9 and remove windowshade prefpane and window shade ape files.

Tried twice. Crash suitcase on start. Could be a conflict their.

Posted by: Mark Neal on September 18, 2003 12:53 PM

Love 3.01 especially the double command key tap... really nice (I'm surprised nobody else has ever used this for anything).

My suggestions:

1. Title text should be same size as finder font size

2. Allow auto sorting of MIP windows by app.
-------
another suggestion for another haxie (which would enhance windowshade)...

Give us a haxie to change the style of text under the desktop icons and on dock items. The bold white with black shadow is dog ugly. Why not let us control the font, the background, the transparency, and so on... that would be fantastic. Give us a fe cool precanned ones to play with but also let us roll our own.

Posted by: tim on September 18, 2003 1:09 PM

A few things:

With the Dock, clicking an app's Dock icon will unminimize a window if it is the only window. MiPed windows do not do this.

There also seem to be issues with switching windows in an application. If i launch two Terminal windows and MiP one, I cannot hit Cmd-~ to switch to the other window. Using Terminal's Cmd+1,2,3,etc. feature seems to bring the MiPed window into focus, but there is no way to maximize it from the keyboard. It's nice to be able to minimize windows from the keyboard, but there ought to be a way to maximize them as well.

Posted by: josh on September 18, 2003 1:44 PM

The CWM bug is fixed! Yay! I've been waiting for that.

Posted by: Joe on September 18, 2003 2:46 PM

So, any word on the "doesn't work with X11 b3" bug from 3.0?

Tnx...

Posted by: Brian on September 18, 2003 3:46 PM

Excellent works, guys. Only thing I'd like added is to be able to bring back a MIP' window when you click on it from its app's Dock context menu.

Posted by: Ken on September 18, 2003 6:07 PM

Just found a bug. I set double-command to minimize to the Dock and then tried it out. Unlike the MIPed and windowshaded windows the ones in the Dock don't restore if you tap command twice after minimizing. This isn't a big deal except that it minimizes to the Dock again, creating duplicates. To make this worse it will only unminimize one window. If you accidentally double tap after minimizing the last window you have to quit the Dock to get rid of an extra icon above the trash (Dock is pinned at end on the right side of my monitor).

Great work otherwise though.

Posted by: VGZ on September 18, 2003 8:40 PM

It still needs to be able to magnify the window to 100% of the original!

Posted by: on September 19, 2003 3:43 AM

I hate to complain here, but certain windows (iTunes, iPhoto, among others) Do not listen to the double-tap key commands. They minimize via the older methods, though.
I'm also having the arrangement problems with the windows stacking on top of each other instead of arranging. Looking forward to a bugfix, guys.

Posted by: Tom Burns on September 19, 2003 8:04 AM

Great work again. Fixed a problem with powerMail email composition window not responding to mouse clicks when the main window was minimized in place. Hooray.

I am also seeing the collapsed in place windows stacking up on each other. (Until I opened the preferences for Windowshade and they all jumped to the right place. Do you suppose they need adult supervision from the mothership?)

Thanks

Posted by: Jim on September 19, 2003 11:02 AM

Great update. I still can't find files in Finder without it crashing with WSX installed though. Has anybody else experienced this?

Posted by: Matt Martinez on September 19, 2003 11:36 AM

after installing ws 301, meteorologist 130a does not load anymore

Posted by: vitaly citovsky on September 20, 2003 4:46 AM

Needs 2 things
(1) Needs to maximize the MIP'ed window if it's the only window open when an applications icon is clicked in the dock.
(2) drag a MIP'ed window into the dock.

Otherwise, as always another Rock-Solid update guys. Great Job

Posted by: Brandon Delcamp on September 20, 2003 11:27 AM

Both excellent suggestions.

One bug: MIP windows stack on top of each other when you have the option to arrange MIP windows along the left edge starting at the top.

Oddly enough the windows do not stack with any other setting.

This only happens my G5 w/ 23 inch cinema display and not on any other machine.

Posted by: kelly on September 22, 2003 12:15 PM

Here's how to fix this, Kelly. You give me your G5 and I will give you my G4 867 and your problem will be solved.

Posted by: on September 22, 2003 12:47 PM

I am also suffering from MIPed windows stacking on top of each other using the "arrange windows along left edge starting at top" option. I have an 800 MHz flatpanel iMac with SuperDrive.

Posted by: Jeffrey Czerniak on September 22, 2003 3:27 PM

Found another bug. If you restore a MIPed window it doesn't gain focus. Also MIPing a window doesn't change the focus to the next window in that app. This is why you can use the keyboard shortcut to MIP a window and press it a second time to restore it. Please correct this annoying bug in an otherwise great app.

Posted by: VGZ on September 22, 2003 4:46 PM

>Minimize-In-Place windows are being auto re-arranged when you
>expand one of the minimized windows.

Okay, after living with this for some time: Can we please make this an option? Bevore that, I used to have some specific windows minimized in some specific places. I could click on them without actually looking at them and then minimize them back to where they came - muscle memory and all that. That's not possible anymore, since the minimized windows will shift their positions around.

Posted by: LKM on September 22, 2003 10:38 PM

Sweeet!

I haven't been a fan of this implementation of MIP. But I do like this whole Press Control/Command button twice feature! It really is faster! What will you think of next?

Posted by: Jason Anderson on September 23, 2003 12:13 AM

How is the compatibility of WSX 3.0.1 with the latest OS X update: 10.2.8 ?

Any noticeable conflicts with it?

Posted by: Kaleb Wyman on September 23, 2003 1:03 AM

WSX 3.0.1 seems to work fine with 10.2.8.

As for bug reports / enhancement request, I have two, both re: keys pressed twice (Cmd & Ctrl):

- Double-press speed should be adjustable. Just as Mac OS' mouse double-click speed has always been adjustable, this should too - so as to avoid the annoyance of accidentally triggering WSX when you don't want to.

- Presses of Cmd or Ctrl, shouldn't be considered by WSX, as part of any double-press, *if* they're pressed in conjunction with some other key. Right now, the second keypress *is* considered, *even when* it's held down in combination with another key, i.e. you've pressed Cmd-UpArrow or whatever.

It's funny, unconscious behavior -- like, pressing the command key absentmindedly once, and then releasing, before you actually press it again to actually do something (like, cycle windows, or scroll down Cmd-DownArrow, or whatever) -- well, that unconscious habit, now becomes interpreted by WSX and trips you up. By "you", of course, I mean "me", but this may also describe you, too.

Anyhow, I see no reason Cmd or Ctrl should be considered as part of WSX's "double-press" if it's held down in conjunction with an actual key; in other words, they should only be considered as triggers to invoke WSX if they're held down *on their own* w/ no other keys held down.

Similarly, adjustable double-press speed would go a long ways towards making the WSX's double-press responsiveness feel "just right".

Thanks for an otherwise great update (notwithstanding MIP bugs mentioned above which I've also experienced, and which hopefully will be easy to fix).

Posted by: Ed Mechem on September 23, 2003 10:58 AM

on my machines (g4 duo, 1ghz) WS301 conflicts with fiunder's find function and with burning cds. when i click apple-F or insert blank cd, finder quits. if remove ws301 - all is fine again

Posted by: vitaly on September 23, 2003 3:43 PM

actually, the problems with ws301 and find/blank cd/finder also are present in os 10.2.6. i just reproduced it on my g4 powerbook that is still running 10.2.6

Posted by: vitaly on September 23, 2003 3:55 PM

The broken find has carried over from 10.2.6 to 10.2.8 for me, too.

Posted by: Matt Martinez on September 23, 2003 6:11 PM

funny, I'm running OS X 10.2.8 and WS 301 and I have no problems opening "find" in the finder or burning CDs... do you have something else affecting your finder perhaps?

Posted by: john engler on September 23, 2003 7:19 PM

Nope, it's WSX for sure. If I remove it, find works flawlessly.

Posted by: Matt Martinez on September 23, 2003 8:11 PM

it does that to find/blank cds on my g4 powerbook, old g3 ibok, and two mirror-door 1ghz duos but not on to 867 mirorr-doors duos and not on a 867 quicksilver

go figure.

of course, i i remove the .ape (NOT pref.pane) all is normal again

Posted by: Vitaly Citovsky on September 24, 2003 8:49 AM

my iBook 500 running 10.2.6 has no problem with Find in Finder.

i don't run APE on my G4.

Posted by: petey on September 25, 2003 1:56 PM
Post a comment
Keep comments on topic. If a comment is unrelated to this post, it may be removed or moderated.





Remember Me?

(you may use HTML tags for style)