Opened 10 years ago

Closed 10 years ago

#6928 closed enhancement (fixed)

Another 'active' colour for Stack & Tile could send a better message.

Reported by: Meanwhile Owned by: czeidler
Priority: normal Milestone: R1
Component: Add-Ons/Decorators/Default Version: R1/alpha2
Keywords: Stack&Tile, SATDecorator Cc:
Blocked By: Blocking:
Platform: All


At the moment, Stack & Tile uses the red colour to indicate that a window is at a position to automatically stack/tile. I believe green would be a better choice:

To stack/tile, the user needs to perform a 'keypress & drag' combination.

This means the chance that Stacking & Tiling occurs by accident is virtually zero. So the user is expecting something as a result of what he consciously chose to do, and only needs a visual confirmation of it (through colour).

In such a case (with that user's state of mind), a green colour would suit better than red, since red psychologically says 'Stop', 'Look out', 'Error', 'Warning' etc.

Those are deterring (rather than confirming) messages that send the exact opposite message of what you want to achieve.

I'm not saying green should definitely be it, but red is too wrong to not correct, IMHO. And it's an easy fix ;)

Change History (4)

comment:1 by bbjimmy, 10 years ago

SAT needs to insure that the confirmation color is different from the current tab color. No matter what color is default for the stack/tile action, some users will use that color for their window tab / boarder using the Appearance preflit.

comment:2 by Meanwhile, 10 years ago

A solution could then be to make SAT's confirmation colour customizable from within the Appearance preflet and have the default not in red?
(BTW, 'confirmation' colour sounds better than 'active' colour, thanks)

Last edited 10 years ago by Meanwhile (previous) (diff)

comment:3 by diver, 10 years ago

Component: Servers/app_serverAdd-Ons/Decorators/Stack And Tile
Owner: changed from axeld to czeidler

comment:4 by czeidler, 10 years ago

Resolution: fixed
Status: newclosed

Think this is more or less fixed.

Note: See TracTickets for help on using tickets.