On 9/6/06, MenTaLguY <mental@...3...> wrote:
On Wed, 2006-09-06 at 00:05 -0300, bulia byak wrote:
I also propose to rename the "Drag" spinbutton into "Wiggle", with a reversal of values (i.e. drag:0 == wiggle:1 and vice versa). I think this would be much more descriptive. Thoughts?
Hmm, I don't know. "Wiggle" suggests active movement, like "tremor".
And that's exactly what it does when you lower the drag (try it).
If I were to pick an alternate/more descriptive name for "drag" it would probably be "friction" or "damping".
My goal is not to find a synonym, but to give a better idea of what to expect when you change the value away from the default drag=1.
Incidentally, what are we going to do about the width of the toolbar? At this point, the minimum window size almost completely fills my laptop display. That's just too much.
In a word, we need better controls. Text labels are awkward and spinbuttons are very inconvenient. Small sliders with graphic icons would be much much better. Besides the sliders would be stackable in stacks of two (without increasing toolbar height), which would solve the toolbar width problem.
Similarly, I'd love to steal the small edit controls from Xara toolbars, where they are also stacked in twos. Too bad our widget libraries are not compatible...
One option might be to make the vertical size of the secondary toolbar variable between tools, and add a second row for tools that needed it, but if we were to do that, we'd need to make sure to scroll the viewport to compensate, so that the actual drawing didn't shift around.
If we eventually decide to go with that, I'd rather delay this change as much as possible, until such a time when _most_ of the tools need two rows, in which case the switch would be much less of a hassle.