Replies: 2 comments
-
I think it's fine.. because you shouldnt make assumptions about how people are going to use the software.. it doesn't hurt anyone and everyone knows how to use it it's up to the user to put in the field what they really need todo, i really dont like writing software that makes assumptions, this is not a bug - it's more of a feature |
Beta Was this translation helpful? Give feedback.
0 replies
-
4em to 5em yeah, i'm not a designer, if you are a designer with proven, well used projects in your experiences please open a PR |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
@dgtlmoon - I was going to suggest that these input boxes need to be wider (in the version that was just pushed to Docker), but then realized that with the new UI there's no reason to have more than 59 in the minutes field. But when converting from the old UI to the new, it might be confusing to some users, especially non-developers. I'm sure how much trouble it would be to convert the times to the lowest common denominator when someone installs the version with the new UI (e.g. 1440 minutes = 1 day, etc.). You could also change the width of these boxes from 4em to 5em so the whole value is visible, if the field is going to allow more than a 2-digit value.
Beta Was this translation helpful? Give feedback.
All reactions