Numeric control scroll wheel changes active digit

[tstalcup_apre]

I think the behavior when using the mouse wheel to adjust values in any numerical box (numerical control, array index, etc) has changed in the last version or two.

Current behavior:

Start at value of 98 with cursor to right of 8

Scrolling the mouse wheel up produces:  99, 100, 110, 120, 130

Changing directions and scrolling down produces:  130, 120, 110, 100, 90, 89

Is there a way to change the default behavior such that it doesn't change the active digit?  This makes the mouse wheel practically unusable if you're trying to adjust between 95 and 105, for instance.

Thanks!

Thomas

[RavensFan]

Consider using an event structure configured for the numeric's mouse wheel.  You could implement your own incrementing.

But I think you are going to need to do some other things to make it behave the way you want.

While it is kind of nice to have the ability for the scroll wheel to change the numbers, honestly, I don't think I've ever truly needed it either in its current form, or any other.

Take a look at the property node for numerics called BuiltInMouseWheelSupport.  You can disable the mousewheel, or change to OnHover, OnKeyFocus, or both.

If you want the mousewheel to always be next to the ones digit, you could use the propertynode NumericText > Selection and set the start and end point to be the same at a value large enough to put it after the one's digit.

[tstalcup_apre]

Thanks for the response.  I had briefly considered using some sort of event structure workaround, but there are at least a few dozen places in my current vi where this is an issue and it's impractical to create event structures to implement a workaround for dozens of controls.  Plus, I think this is new behavior for the scroll wheel, and if you use the arrow keys on the keyboard you get a different behavior - which is the one I want.  I'm pretty sure in previous versions (2016?  2018?) mouse wheel and keyboard up/down worked the same.  I know, I should just use the keyboard, but it's just more efficient to use the mouse rather than switching mouse/keyboard/mouse/keyboard and I was hoping there was just a checkbox somewhere like "use old style mouse wheel" or something similar.

To make a comparison, it's why I like scrolling through long webpages with the mouse wheel rather than the keyboard.  You can roll the wheel fast to scroll a long distance, then go slowly when you get to where you want to read details.  You can also use the keyboard arrows to scroll, but then you have to push the down arrow many, many times as opposed to just one swipe of the wheel.

Also, this is not just the one's digit, it's any digit I want to adjust.  As an example, I have a control that sets the end of travel for a scan arm.  Values range from 35000 to 120000.    I start at 97388, want to scroll up by 1000's to examine the instrument behavior.  I click between the 4 and 3, and roll the wheel up: 

97388

98388

99388

100388

110388

dang, that last jump of 10k counts when I expected 1k put me too far.  Reverse direction and scroll wheel down:

100388

90388

ok, now after scrolling back two notches on the wheel I'm way below where I started. 

In this example it is impossible to start at 97388, use the mouse wheel to scroll by increments of 1000 and end up at, say, 105388.  

[RavensFan]

You don't need to have multiple event structures.  Or even multiple event cases.  You could have one event structure with one case that is registered for multiple controls.

I don't know whether the behavior has changed somewhere along the line.  Like I said, I have never really used the scrollwheel functionality like this.  And seeing how you don't like the way it is behaving is making me event less likely to ever use it.

It's the weekend and there is less activity on the forums.  Give it some time and maybe someone else with some insight can contribute.

[Frozen]

I assume you are using 2019?

I have checked both 2016 and 2018 behavior and they both operate the same as your original post.

So it appears the behavior has not changed recently.

Hope this helps.

[wiebe@CARYA]

The control's data entry increment might effect this.

The Windows mouse scroll speed might effect this