Can't type in value

[deplanche]

I am trying to get the height for the fire effect, and I can't seem to type in a number there.  I can slide the slider to change the value, but if I try to type in "30" it doesn't work.  I thought I might have hit the num lock button, so I have tried that different ways and with the number pad and the numbers over the letters.  Seems like other effects can be typed in ok, just not there.  Am I doing something wrong?

[Phrog30]

I have noticed there are a couple of textboxes that won't allow manual entry. For now, if you hold left mouse down on the slider you can use the cursor keys for fine movement.

We probably need to create a github issue for this.

Edit: Github issue -- Fire effect height textbox entry #709

James

Sent from my SM-G900V using Tapatalk

[Ebuechner]

Good it wasn't just me I noticed that too using .50

[keithsw1111]

The fire effect text box behaviour is by design ... The height value is only allowed to be between 10 and 100 ... if at any point the value falls below 10 then it is set to 10. Its not ideal from a user experience but it does prevent illegal values. This is the same way every text/slider combo works.

[Phrog30]

Then a value of 22 should be allowed to be entered. The point of his thread, and I verified, you can't enter a value at all (but the slider works). This textbox is not how they all behave. Please try for yourself and you will see.

James

Sent from my SM-G900V using Tapatalk

[Phrog30]

if at any point the value falls below 10 then it is set to 10

I thought about it a second and see what you are saying. If I highlight the current value (example 100) and start typing, I can only type one character at a time. So, no matter what, the value is going to be less then 10. The current validation on this object makes it impossible to enter a value. So, if you can't enter a value in the textbox, why have one? Like I said earlier, the other textboxes (majority) do not behave this way.

James


Sent from my SM-G900V using Tapatalk

[Ebuechner]

I hope you're not suggesting getting rid of the text box. I still want to see the number value of the setting! Greyed out maybe so you know you can't interact with it.

[Phrog30]

I hope you're not suggesting getting rid of the text box. I still want to see the number value of the setting! Greyed out maybe so you know you can't interact with it.

No, I didn't mean to suggest that.

Sent from my SM-G900V using Tapatalk

[Gilrock]

Yeah it would be better if it wasn't trying to validate every keystroke and instead did the validation when it was being committed.  Not sure if that's something we could easily change.  It might take us manually editing 1000 boxes.  I'm sure I could type in "22" if I wanted.  If you have "10" just select the "1" and type a "2" then select the "0" and type a "2".

[Phrog30]

I hope I didn't make this seem like a big deal. We have a few workarounds on this. It's not important, in my opinion. But did want to create a ticket in case you guys get bored. 

Sent from my SM-G900V using Tapatalk

[Gilrock]

We must not have any other boxes that have a minimum value set to something higher than 0 or 1 or we would be seeing this all the time.