un-minimize behaviour

[Todd Slater]

On Fri, Jul 18, 2003 at 05:59:28PM +0200, Jan Eidtmann wrote:
> On Friday 18 July 2003 15:48, Biju Chacko wrote:
> > On Fri, 18 Jul 2003 15:35:49 +0200, Jan Eidtmann wrote:
> > > when i minimize a shaded window and then un-minimze it, it should
> > > be un-shaded too IMO.
> >
> > why? thats not very logical! If I shade something I expect to *stay*
> > shaded until I tell it to unshade.
> >
> > -- b
> 
> not true, when i click the minimized app in the taskbar its most likely 
> that i want to do something with that window. now i have to click the 
> taskbar and the unshade shortcut/button/windowbar too.

I might want to do something with it like kill it or move it to another
workspace, and in both of those cases I wouldn't want the window to
unshade.

> to me its a more logic behavior to automatically unshade the window. it 
> makes no sense to shade and minimize a window anyway. IMO an shaded and 
> then minimized window is a minimized window only. bacause minimizing 
> and shading is basically the same thing to me, as it "unclutters" the 
> workspace... what do you think?

Sometimes I have a bunch of windows open and I shade one to see what's
behind it. And sometimes I iconify a shaded window just to get it out of the
way. You want I should unshade it first?

I can see how some people might like what you suggest but for me it is
counterintuitive; I would not expect that behavior.

Todd