New bug: using mouse wheel for incrementing

[rubs]

In version 1.7, using the mouse wheel in certain fields does not increment with integer values anymore, at least when using 6-digit precision. Here's an example:

I hope that's clear for you to understand.

[Sean P]

Thanks rubs,

I've reproduced this and passed it on to development! 

[AdamW]

Hi rubs,

This is a deliberate change over 1.6. As an example, incrementing this field by integer values when using inches as a unit makes no sense. Instead we now use an increment based on the number of decimal places set up for the unit in preferences. By default we use ten times the smallest value indicated by the number of decimal places, so 3 decimal places increments in hundredths, 1 decimal place increments in integers, etc.

Also note that using <Shift> increases this base increment by a factor of 10 and using <Alt>  reduces it by a factor of 10.

[rubs]

28 minutes ago, AdamW said:

Hi rubs,

This is a deliberate change over 1.6. As an example, incrementing this field by integer values when using inches as a unit makes no sense. Instead we now use an increment based on the number of decimal places set up for the unit in preferences. By default we use ten times the smallest value indicated by the number of decimal places, so 3 decimal places increments in hundredths, 1 decimal place increments in integers, etc.

Also note that using <Shift> increases this base increment by a factor of 10 and using <Alt>  reduces it by a factor of 10.

Just think about it, a high number of decimal places is for enhancing precision in pixel-perfect designs. Using the mouse wheel on the tab size field is for increasing efficiency. I don't see a relation between the two. Since working with tabs in AD is already very difficult, removing the ability to quickly change tab spacing with the mouse wheel further impairs a very incomplete implementation. The obvious way of doing it, which is dragging the tab stops on screen like everybody else, was never implemented.

In any case, what you guys really should have done was to expose increment values as an user option, not to hardcode it.