[GH-ISSUE #1246] [Bug] Editor - Statistics - duration unit wrong #921

Open
opened 2026-02-26 09:33:01 +03:00 by kerem · 3 comments
Owner

Originally created by @fireattack on GitHub (Nov 5, 2023).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1246

Originally assigned to: @NickeManarin on GitHub.

Describe the bug
The durations are in seconds (s), not "m".

To Reproduce
Steps to reproduce the behavior:

  1. Go to Editor -> Statistics
  2. Check toolbar

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots

bug

Desktop (please complete the following information):

  • OS: Windows 10
  • Version 2.39
Originally created by @fireattack on GitHub (Nov 5, 2023). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/1246 Originally assigned to: @NickeManarin on GitHub. **Describe the bug** The durations are in seconds (s), not "m". **To Reproduce** Steps to reproduce the behavior: 1. Go to Editor -> Statistics 2. Check toolbar **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** ![bug](https://github.com/NickeManarin/ScreenToGif/assets/4130991/c1e5828c-0d87-4046-9f15-35543d5bcfc6) **Desktop (please complete the following information):** - OS: Windows 10 - Version 2.39
Author
Owner

@NickeManarin commented on GitHub (Nov 7, 2023):

It's read as 0 minutes, 0 seconds, 50 miliseconds, and since I'm showing the minutes part, the label it's shown as "m".

I can change to reduce the minimum level to seconds (when less than 1 minute), then it will display as: 00.050 s

<!-- gh-comment-id:1799201159 --> @NickeManarin commented on GitHub (Nov 7, 2023): It's read as 0 minutes, 0 seconds, 50 miliseconds, and since I'm showing the minutes part, the label it's shown as "m". I can change to reduce the minimum level to seconds (when less than 1 minute), then it will display as: 00.050 s
Author
Owner

@fireattack commented on GitHub (Nov 10, 2023):

Thanks for explanation!

I'd argue even if it's more than 1 minute, say, 2m5s, a notation of "02:05.000 m" is still weird, if not wrong (like you won't write 2h10m5s as "02:10:05.000 h").

Since it's just a standard timestamp format, and the inclusion of milliseconds makes it not ambiguous, maybe we can just remove the unit?

<!-- gh-comment-id:1805272584 --> @fireattack commented on GitHub (Nov 10, 2023): Thanks for explanation! I'd argue even if it's more than 1 minute, say, 2m5s, a notation of "02:05.000 m" is still weird, if not wrong (like you won't write 2h10m5s as "02:10:05.000 h"). Since it's just a standard timestamp format, and the inclusion of milliseconds makes it not ambiguous, maybe we can just remove the unit?
Author
Owner

@pawlos commented on GitHub (Nov 10, 2023):

Tbh, when I briefly looked at this in the code, to me it should also be w/o any unit

<!-- gh-comment-id:1806292514 --> @pawlos commented on GitHub (Nov 10, 2023): Tbh, when I briefly looked at this in the code, to me it should also be w/o any unit
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ScreenToGif#921
No description provided.