Arrow key in integer field broken

If you put the cursor in a numeric field that is an integer and hit up or down arrow, it increments or decrements and then immediately disables the field input.

The initial description of this feature is to change a number with precision and decimal numbers come to mind, of course. But I think it should work on integers as well -- which you might also want to increment by 1 or 10, etc.

If you put the cursor in a numeric field that is an integer and hit up or down arrow, it increments or decrements and then immediately disables the field input.

The initial description of this feature is to change a number with precision and decimal numbers come to mind, of course. But I think it should work on integers as well -- which you might also want to increment by 1 or 10, etc.

It works for me. You have to insert the cursor, not merely give focus to the field. Then, left and right arrows set the increment value by powers of 10, and up/down increment/decrement.

Are you using default keybindings?


Sent from my iPad using Tapatalk

Thanks for trying it! It works for me on non-integer fields all the time, and I'm doing the same thing in the other fields. The only difference is that it's an integer field (i.e. no decimal point or digits after the decimal point are in the field). I'm not trying to increment the 1's or 10's of a decimal field, if that matters, but just an integer field with no decimal points.

I'm not seeing any issues in Studio 17b9 for Windows. The feature is working as it should.

Can you specify what page and fields you're testing?

Jim, it's actually a little hard to find an integer field.

Create a Text (not Text+) node.

Put some text in it.

Put the cursor in the Size box -- note that it is an integer like "96" -- after the last digit (i.e. after "6").

Hit up arrow. It changes to 97, but note that the cursor disappears even though the box is still red and the red focus line is still above the Inspector..

Hit up arrow again, and you will be jumping to next edit in the timeline.

Oh yeah. You get one change and that's it. Back to the timeline.

It could be a Text node issue, but I think the up arrow code gets confused because there's no decimal point. I think I've had the problem on other integer fields but they're rarer than I thought so I haven't pinned that down.