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
So, just to clarify, when starting a new segment you want to have the ability to use a pre-defined segment name for a new segment? That sounds like a good idea.
Any reason you're not just using sub-segments by continuing an existing segment, though?
Fair question. I actually missed that functionality as the additional
buttons for sub-segments do not appear when a timer is running.
I will actually try using sub segments and see how that goes.
But, yes, my initial query was for a pre-defined *segment name*.
Thanks for the quick reply!
Dion
On Fri, Nov 4, 2022 at 2:28 PM Ellpeck ***@***.***> wrote:
So, just to clarify, when starting a new segment you want to have the
ability to use a pre-defined *segment name* for a new segment? That
sounds like a good idea.
Any reason you're not just using sub-segments by continuing an existing
segment, though?
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APY26UDBMLLMALOAKBN5YTTWGVIWDANCNFSM6AAAAAARXNFYBY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
Future suggestion: provide a list of segments to choose from when starting a timer.
Perhaps based on existing segments in the current timer block, with an option to type in a new one.
Or, based on a pre-defined list.
When switching between the same named segments during the work day, having to type them in can lead to errors.
Thanks!
The text was updated successfully, but these errors were encountered: