Consider changing default int spinbox step size to 1

[jni]

It is nicely documented that the default step size for the spin box is adaptive:

step (float, default: Undefined ) – The step size for incrementing the value, by default adaptive step is used

However when I just had a widget annotated as int recently I thought I was going crazy when all of a sudden the + would skip 10 numbers. Would it be possible/desirable to change the default to 1 when the data type is int? (For floats, indeed, the situation is more ambiguous.)

[tlambert03]

i'll leave it up to you and @Czaki to decide that. I believe he was the one who proposed using adaptive step as default in #403. i'm fine without whatever you guys want

[Czaki]

My experience is that when you operate with a big value it is more common that you want to change using bigger steep.

For example, if you have a threshold value of 8000, it is more common to change it to 8500 than to 8002.
Of course, if you try to select a socket number, it may be confusing.

But still for me, when a user creates a function widget, the expected step should be dynamic.

[jni]

@Czaki but things like magnitude (thresholds) are usually represented as floats rather than ints, no? In many cases, ints are IDs/categories, and then skipping them makes no sense. (This was the case in the widget I was trying to make for inspecting track IDs. The same would be true for Labels, point IDs...)

I think there is something fundamentally different about how the spinbox should treat ints (where there is a natural step) and floats (which are continuous).

[Czaki]

@Czaki but things like magnitude (thresholds) are usually represented as floats rather than ints, no? In many cases, ints are IDs/categories, and then skipping them makes no sense. (This was the case in the widget I was trying to make for inspecting track IDs. The same would be true for Labels, point IDs...)

I meet people, who works mainly on uint16 data and are using int as a threshold annotation.

But In general, I agree with you that we may suggest using float in such situations (in documentation). We may also keep an option to enable adaptive steep using proper annotation.

[kephale]

For int my expectation is +/- 1 for buttons, unless the specific widget has different settings. I think folks will still want to be able to have their int's use an adaptive step size, but I don't expect adaptive step sizes to be the default.