Numberstepper - What's the point of the precision value if the step is what determines the precision?

[Lasercar]

Title.

I have this number stepper that I'd like to have a precision of 1 (decimal point), and a step of 1, but the only way to get it to have a precision of 1 is to make the step a precision of 1 (aka 0.1), defeating the purpose/point of the precision value altogether, aside from displaying the precision.

[ianharrigan]

i feel like there was a discussion about exactly this recently on the discord - do you have an example of what you mean (just so i know we are talking about the same thing).

Cheers,
Ian

[Lasercar]

Sure, for example, I encountered this issue while I was working on this: FunkinCrew/Funkin#4148

Basically I have two number steppers a used for a delay and tween thing for a fade in for this music track, expressed in seconds. I'd like the user to be able to use the up or down buttons to increase it by a second, but also be able to set fractions of a second too if they so choose. But, the only way to allow fractions of the second (/float) is to have a step that's a fraction, aka 0.1.

You can see in the demo video how I had to resort to entering in 5 seconds manually because the video would end up bigger than 10MB if I instead clicked 50 times.

Oh, also, this isn't relevant to this issue but there's this problem where the focus manager seems to always return false even when in input fields and I don't know if it's a haxe ui problem or with the way the input fields here are set up:
FunkinCrew/Funkin#3923 (comment)

[Lasercar]

Huh, it seems to be fixed now in the git version of haxe ui?