I was chasing against some weird Mail.app bugs caused by WindowShade X (collapse window, expand window, double-click a message - new window with the message will not appear until you switch out of Mail.app and switch back) and did some serious investigations on the Cocoa side of things. It turned out the Cocoa WindowShade X side can be made much more cleaner and efficient (and get rid of the above mentioned bug(s)). So here I am, started a little rewrite/cleanup of the code for Cocoa part of WSX.
1.5 years ago, when I was just starting on WindowShade X, we had much less advanced tools to do stuff, so some parts of WSX (especially on the Cocoa side) were pretty... hackish. They work fine, but there is a better way of implementing it -- I see it now. The code carried on since then and now I finally can dedicate 2 days to completely rewrite the thing.
On that matter, a quick poll for WindowShade X users:
- Try Windowshading a window;
- Click on the Minimize to Dock widget or Make Transparent;
- The window will unshade and either fly to Dock or become transparent.
Is that the right behavior? Shouldn't it just unshade? What to you think?
Related:
- Hiya Kids, it's Theming Time! - Oct 06, 2009
- Mighty Mouse with Some Theme Sauce - Jun 02, 2009
- WindowShade X 4.3 - Apr 24, 2009
- Sound of the Underground - Apr 20, 2009
- Welcome back. - Apr 17, 2009
No, I like the current behavior. I actually use it quite often - usually I windowshade, then realize "no it's still using too much room" and minimize to dock after that.
APE rocks, but you need to work on the documentation and template :)
Posted by: Nicholas Riley on January 19, 2003 5:52 PMI think the current behavior is correct. At least it does what I'd expect. :)
Posted by: Philippe Martin on January 19, 2003 6:06 PMyep, does just what i'd expect it to do... the current behaviour seems perfectly correct to me. :)
Posted by: bender on January 19, 2003 7:44 PMHmm... Seems if I shade a window, well, I want it shaded - even when I minimize it to the dock, make it transparent, or hide it (which I have the yellow button set to do).
Couldja add some sort of option for this? For example, sometimes I have a bunch of browser windows open, and I'd like to hide the app. If I click on a browser window that ~isn't~ shaded, the app hides, and shaded windows stay shaded. Great. If I click the yellow button of a window that ~is~ shaded (to hide the app) that window I just clicked on will unshade... Oig.
If you don't get it Slava, you know where I live. ;p
Posted by: Dan on January 19, 2003 11:00 PMI think it works correctly right now. Default behaviour is to shade/unshade on titlebar double click, and to minimize on minimize widget click. And it seems that minimize and shade should be mutually exclusive, as they are currently.
Posted by: Mike on January 20, 2003 12:13 AMNeil: yeah, we're aware of it, and still trying to fix it fully (it has transformed into something new in the update I am working on, since it now properly handles "attached" windows (particularry sheets issue in Word X) - so the bug right now looks like this: begin renaming a file in the Finder, shade the window, unshade it back - the file name will be invisible. Click anywhere, it will become visible again. Still not ideal, but better than it was in 2.1.1
Posted by: slava on January 21, 2003 2:26 AMMike is right
i think it works fine the way it is
by the way, is upgrading free? i paid for my windowshade...
Posted by: jack on January 21, 2003 5:03 PM*cough*Option to automatically set all newly opened windows as transparent*cough*
;)
Posted by: VirtualWolf on January 21, 2003 9:07 PMI think it works correctly already as well. Mike summerized it best
"Default behaviour is to shade/unshade on titlebar double click, and to minimize on minimize widget click. And it seems that minimize and shade should be mutually exclusive, as they are currently."
Thanks for all the great work! I can't wait for Minimize in place!
Keep comments on topic. If a comment is unrelated to this post, it may be removed or moderated.
