"bulia byak" <buliabyak@...>
> On Tue, Jul 1, 2008 at 3:37 PM, Terry Brown <terry_n_brown@...> wrote:
>> It's another type of custom ctrl I guess, but Blender uses ctrls
>> that look something like this
>> < 45.3 >
>> Clicking on the arrow heads changes the value by a set amount.
> This is what we always had. All numeric spinbuttons have those arrow
> buttons. The idea is to make it possible to use dragging, not
> clicking, which is much faster and easier (though less precise).
>> Clicking on the control but not on the arrowhead or number and then
>> dragging the mouse across the screen changes the number
>> proportional to the mouse movement, as if you'd grabbed a large
>> imaginary invisible slider/scrollbar type control.
> And this is what we don't have, and what has been proposed more that
> once. But I think it's a change GTK should make in their spinbutton
> control, then we get it for free.
> Still, for some values a hslider is even better than this, as it
> gives a clear visual clue as to where in the allowed range your
> value is. Its only disadvantage is you cannot type a value, but I
> think we can live with that for things like Width or Force.
I think losing the ability to enter a value numerically is a big
problem for usability, since it reduces reproducibility (if you move
the slider away from your favorite value, can you find it again?), and
as you said it is useful for documentation.
As for the blender ctrl, i guess the position of the number within the
control reflects the position of the value within the allowed
interval, which alleviates your criticism.
Example: <-----------90-> versus <-10----------->
Dragging is still possible, but it is a tad unintuitive as you have to
click out of the slider (on the dashes on my example) to start
drawing. Maybe this could be remedied by having a drag surface around
the numeric value where one can grab the slider to drag (pipes on my
<-----------|||90|||-> versus <-|||10|||----------->