Repository navigation
Replies: 2 comments 1 reply
|
The running activity card shows the time remaining for a duration goal, but it does not display an estimated clock time for when the goal will be reached. The running goal display calculates For example, applying that calculation at 14:00 gives: python3 - <<'PY'
from datetime import datetime, timedelta
now = datetime(2026, 10, 1, 14, 0)
for label, goal_minutes, accrued_minutes in [('session', 60, 10), ('daily', 60, 20)]:
remaining = goal_minutes - accrued_minutes
print(f'{label}: {remaining} min remaining, target at {(now + timedelta(minutes=remaining)):%H:%M}')
PY
session: 50 min remaining, target at 14:50
daily: 40 min remaining, target at 14:40So you can add the displayed remaining time to the current clock time for an ETA, assuming the activity keeps running. A count goal has no time based ETA. This follows the running goal calculation and its running card tests. |
|
@Arthur031221 thanks for your answer 👍. I also agree that your code looks to answer my needs with its ' target at 14:50' output. @Razeeman: PS: Sorry, but I don't yet have the technical skills nor enough knowledge of the app's structure to add this feature myself (even with the help of AI 😋). |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I'm used to run "GPS Navigation apps", these app always display an "ETA" (estimated time of arrival).
In ASTT, when recording an activity with a defined objective, is it possible to see somewhere in the app the "estimated target time" that's to say the estimated End time of the activity, if is continues, when the defined goal will be reached?
Thanks for your answers.
All reactions