Le 23/05/2012 17:31, Stéphane Ducasse a écrit :
It makes the default interaction a lot more reactive (i.e. you notice
on screen when you are pressing on a button).
Now with your change I do not understand why and when a button is
becoming blue.
I think this is when the button has a true state, as used by the
getStateSelector of the morph. This is visible in the Hierarchy/Flat
button in Nautilus, where Hierarchy is state == false, and Flat is state
== true (and has the blue color).
In the case state true, PharoTheme may be falling back on the colors of
the WateryTheme.
Another bug shown with my change is, if you start to scroll with the
slider, it depresses correctly, but, as soon as you move outside the
bounds of the scrollbar, even while pressing the left mouse button, then
the slider goes back to the "not pressed" state while you are still
scrolling up or down.
Side note about UI changes in Nautilus: will there be any changes
about the Groups/Hierarchy/Class/Comments buttons ? I have a hard time
getting used to them (lack of selection/state clues, unusual behavior
for buttons).
Yes we all are saying that this is not working since we do not know if
the state we are in.
Change with "toggle" buttons instead ?
Playing with the Nautilus GUI, more interesting behavior(s) :
* Select an empty package (_UnpackagedPackage)
* Hierarchy button becomes disabled
but
* Instance / Class button is still enabled
* Comment button is still enabled
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
