You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great to be able to specify not only the end time of the timer, but also the start time, which is different from the current moment.
In my case, it is important to be able to specify a start time that has already passed, for example, the beginning of a week, month or season.
This is useful if, after restarting the computer, I want to resume timing without losing progress.
For example, when half of the month is already over, I don’t want a restart. I want to see how the whole month is divided into two parts: the past and the remaining.
The text was updated successfully, but these errors were encountered:
HiRolla
changed the title
Add command line option --started-at
Add command line option --start-time
Oct 30, 2024
As I understood the point is to measure time passed up to this particular moment? It looks like a task tracker responsibility and and not a timer's one.
the point is to measure time passed up to this particular moment?
First of all, it is important for a better sense of time when looking at the progress bar. This option would allow me to keep a visible time scale. For example, 100% = the whole working day. Then I will be able to see time behind and ahead with a clear and already familiar scale and speed of progress.
It would be great to be able to specify not only the end time of the timer, but also the start time, which is different from the current moment.
In my case, it is important to be able to specify a start time that has already passed, for example, the beginning of a week, month or season.
This is useful if, after restarting the computer, I want to resume timing without losing progress.
For example, when half of the month is already over, I don’t want a restart. I want to see how the whole month is divided into two parts: the past and the remaining.
The text was updated successfully, but these errors were encountered: