unity-design team mailing list archive

[Thorsten Wilms <t_w_@xxxxxxxxxx>]

On 02/15/2012 10:10 PM, Mark Shuttleworth wrote:
> If I:
>
>   * use window A1 from app A
>   * then maximise window B1 from app B so I cannot see A1
>   * then raise window A2 from app A
>   * then minimize A2
>   * then click on the icon for app A
>
> .... I would still want to see A2, even though I minimized it, because
> it's the *last-focused window of app A".

But if you:
* have overlapping A1 and A2, A2 focused
* minimize A2
* maximize B1
* click the icon for A

shouldn't it be A1 that comes up, independent on whether it gained focus 
when A2 was minimized?


> MPT can probably point to it, but there's more research that people
> don't understand the difference between minimising and closing, and
> "just want it back" when they click on the app icon. So that's what we
> should give them :)

If that problem is really widespread and persists with a significant 
number of users, wouldn't that suggest that Close and Minimize should 
make way for a single "Hide"? Provided that application start/stop is 
managed somewhat independently and state is restored, removing the 
difference in outcome close and minimize have now.

Actually, if that can be accomplished in a non-leaky way, it would 
remove hassle for everyone (except control freaks and zombies).

There is of course a class of service-based applications that require 
explicit start/stop, like IRC presence and checking email periodically.


--
Thorsten Wilms

thorwil's design for free software:
http://thorwil.wordpress.com/