Numeric Value Editor Considered Harmful

[buserror]

Considering for example the "Bars" field in the track list, if you click on it, you are suposed to want to edit it..

However, if just *single* click rapidly - without moving the mouse - on the "top" part of the field (as if you want to edit the value using the keyboard, due to the problem described in the next paragraph), the value is incremented before becoming editable. Same applies for the bottom part of the field.

Also, the way one is suposed to click & drag the mouse to change the value is particularily lame, one flick of the mouse changes the value by huge numbers, while all one wanted was to change it a little.

This problem is tolerable for some values, but say the time stamps in the event window gets resorted with the new value, wich makes editing very challenging indeed.

[Jerm]

Try clicking and typing in the value. Very easy and standard for most macintosh apps.

[buserror]

what I'm saying is that clicking in the wrong part of the number ALREADY changes the value by +1 and -1, even before you get a chance to type anything.

Say, if "0" is displayed, do a single click in the 2 pixels on top of the 0 will increment the value, and clicking in the bottom part will decrement the value.

and that before the value gets the focus allowing you to type a number.

I think you shouldn't change the value until ::GetDblClickTime() ticks, that won't affect someone clicking + dragging a lot, but that will prevent that behaviour.

[Jerm]

I understand and appreciate what you are saying but the way it works makes it easy to increment and decrement a value quickly.

We would need more feedback on this before changing it.

It should be noted that the value changes fast only when the input range is large. For example, if the input range is 0-127 then the value will change a lot more slowly than if the input range is 0-100000000. This may be something that should be changes. Perhaps it should work such that the value changes at a constant rate regardless of the input range.

Personally I think that would be a better change.

We are open to input on this issue. Hopefully others will comment.

[Fred]

The main problem is that clicking a field sometimes changes the value. This is not standard Mac behavior and needs to be corrected.