Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User Interface: Time Codes Constrained? #256

Closed
jlpoolen opened this issue Jan 14, 2023 · 5 comments
Closed

User Interface: Time Codes Constrained? #256

jlpoolen opened this issue Jan 14, 2023 · 5 comments
Labels
bug javascript Pull requests that update Javascript code usability Usability / user interface improvements

Comments

@jlpoolen
Copy link
Contributor

Under prior versions, I could select a start and stop time down to the second, that allowed me to determine the precise stop/start points of videos which I could then download.

Now when I try to change the numbers, i.e. 09:28:25, in the first "Time" field, the interface will not allow me to specify the seconds, e.g. 25, but reverts to another number, e.g. 01.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Moonfire main web page
  2. Select camera, and then try to enter a date in the first "Time" field
  3. "Time" field will not accept for input, or allow me to change the seconds field to what I want, e.g. 25.

Expected behavior
The ability to set HH:MM:SS to the second.

Screenshots
firefox_2023-01-14_11-55-58

Server (please complete the following information):

jlpoole@pi:/usr/local/src/moonfire-nvr $ date; git describe --dirty; moonfire-nvr --version
Sat 14 Jan 2023 12:02:33 PM PST
v0.7.5-38-g2667dd6
moonfire-nvr 0.7.5
jlpoole@pi:/usr/local/src/moonfire-nvr $

Desktop (please complete the following information):

  • OS: Windows 7
  • Browser Firefox
  • Version 108.0.2

Additional context
I upgraded recently and just noticed this change in behavior.

The ability to select start and stop times is extremely helpful in creating videos which do not have any wasted time before or after the desired action being documented.

@jlpoolen
Copy link
Contributor Author

Also, I've tried using destructive backspace and the arrow key to alter the seconds ("SS") value and the field will not let me do so.
firefox_2023-01-14_12-10-30

@scottlamb
Copy link
Owner

Thanks. This looks like a problem in the @mui/x-date-pickers component I'm using; I reported it there. I've noticed that while you can't backspace, you can use the left arrow and then type over the existing seconds value.

@scottlamb scottlamb added bug js usability Usability / user interface improvements labels Feb 13, 2023
@jlpoolen
Copy link
Contributor Author

The work-around is to create the date sequence, i.e. 10:20:03, in a text editor and then copy paste the value into the field.

@scottlamb scottlamb added javascript Pull requests that update Javascript code and removed js labels Sep 30, 2023
@jlpoolen
Copy link
Contributor Author

Just a heads up: I upgraded today, October 14, 2023, and the problem with the seconds field not accepting what I key in when just the two seconds digits are highlighted continues.

@jlpoolen
Copy link
Contributor Author

Thanks. This looks like a problem in the @mui/x-date-pickers component I'm using; I reported it there. I've noticed that while you can't backspace, you can use the left arrow and then type over the existing seconds value.

Somehow I missed your suggested left-arrow work-around and tried it successfully now; it worked. Thank you!

scottlamb added a commit that referenced this issue Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug javascript Pull requests that update Javascript code usability Usability / user interface improvements
Projects
None yet
Development

No branches or pull requests

2 participants