Incremental input option for vertices count in Star panel
-
@Boldline said in Incremental input option for vertices count in Star panel:
@Subpath said in Incremental input option for vertices count in Star panel:
Works with the Cursor Keys Up ( increases )
and Down ( decreases )ok I see that now, if I highlight it first, I can use the arrow keys to adjust it incrementally. thanks!
works here for me even without highlighting
-
@Subpath @vectoradmin it does not seem to work that way for me unless I highlight the number first. Tried it a couple different times to see
-
works here, i use VS 1.1.020
-
@Subpath yeah I use the same build, but you are on windows and I am on mac - so that is potentially the difference
-
@Boldline For me the number scrolling with keys works without highlight. Is this in a panel or in a modal view? (send a screenshot).
-
@vectoradmin I just figured out the issue - I had the slider active and so it was not letting me use the up and down arrows. When clicked off to hide the slider, I could adjust normally with the arrow keys again with and without the number being highlighted
-
@Boldline yes, if the slider popover is active, it will consume the key input.
-
@vectoradmin said in Incremental input option for vertices count in Star panel:
@Boldline yes, if the slider popover is active, it will consume the key input.
I could still access it ok even when it was open
-
In most of my interface the increase/decrease arrows don't work. When I press it , it immediately shows the slider. Only some of the arrows work.
-
@Devil-Dinosaur When pressing the up/down arrow button with the mouse it does open the slider, that is by design.
I was referring to pressing up/down arrow keys on the keyboard.The editors where the up/down arrow buttons work as scroll buttons are a bit different:
- Vertices field has a popup slider.
- Level field has an up/down arrow for scrolling.
I will try to find a way to have both of these options, the problem is that I have not yet found a good design, and adding two buttons to each field is not the way to go.
