| | 14 | |
| | 15 | If you really want to use Pulses, for a good user experience you should limit the use of them to ongoing processes that end by itself. |
| | 16 | |
| | 17 | For instance, Mac OSX's system shutdown has a two minute delay that's announced by a window. |
| | 18 | |
| | 19 | This window has a button that you can click if you want to shut down the PC by yourself (and don't want to wait before the two minutes are up). This button is animated as a pulse, with a very appropriate one second (or so it seems) interval. |
| | 20 | |
| | 21 | As with the red colour from Stack and Tile, a pulse in Resizing Management expresses way too much urgency for the situation, since there is no time limit. |
| | 22 | The pulse would not only have no real function, it would suggest urgency that doesn't exist. This means a disturbance in the user's work flow. I know Zeta had it, and I remember what impression it left on me (not very positive). |
