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

Multiple Concurrent Timers #128

Open
nelsonic opened this issue Apr 13, 2015 · 7 comments
Open

Multiple Concurrent Timers #128

nelsonic opened this issue Apr 13, 2015 · 7 comments
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! MVP

Comments

@nelsonic
Copy link
Member

@iteles similar to how you feel about categories,
I feel that having only one active timer severely limits the usefulness of this app.
We need to get votes on this from people using the app.

@nelsonic nelsonic added enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! discuss Share your constructive thoughts on how to make progress with this issue MVP FrontEnd labels Apr 13, 2015
@nelsonic
Copy link
Member Author

Maybe giving people the <option> of running multiple timers concurrently isn't such a good idea...

Should people run more than one timer at the same time...? #discuss

@iteles
Copy link
Member

iteles commented Apr 30, 2017

I'm trying to think of good examples of when this would be useful (i.e. when you'd need to categorise a task as two different things) and I keep thinking that if this is the case you need a better categorisation system.

We're trying to encourage focus , which would imply working deeply on one thing at a time.

@sohilpandya
Copy link
Member

I am unsure about whether users should be allowed to run multiple timers at all. Does it detract from the focus side of things? IMO it does.

@iteles iteles removed the FrontEnd label Nov 12, 2019
@iteles
Copy link
Member

iteles commented Nov 13, 2019

Working on one task at a time means one timer at a time. We haven't found a usecase for multiples yet

@iteles iteles closed this as completed Nov 13, 2019
@nelsonic
Copy link
Member Author

The only instance I could think of was running a concurrent timer
for both working on a task and being at a specific location e.g: standing desk.

But we definitely don't need this feature until people using the app request it. 👍

@iteles
Copy link
Member

iteles commented Apr 26, 2023

Somehow this request/feature got lost and we can now run multiple concurrent timers.

Paired with the fact that we don't yet have reordering of items dwyl/mvp#145 (and even once we have it) and that timers that are active timers don't bubble up to the top (I should open an issue for this because there's a bit to think through here), I have already ended up with two 'lost' timers running for a month 😆

(Remember I get hastily interrupted regularly 👶 )

image

Re-opening for discussion.

@iteles iteles reopened this Apr 26, 2023
@nelsonic
Copy link
Member Author

@iteles I use concurrent timers regularly.
e.g. "make lunch" is concurrent with "quality time with child".

But I agree that many people would want to automatically stop one timer when another is running.
This could be defined as a preference in settings.json dwyl/mvp#363 💭
And the default could be to allow concurrent timers
but to prompt the person the first time they try to run multiple concurrent timers.
e.g:

"You have two timers running at the same time, is this on purpose?
You can chose to only run one timer at a time - and automatically stop others -
or have multiple timers running at the same time if you prefer
"

I'm sure we can draft better copy.

The question is: what the default be? 💭

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! MVP
Projects
None yet
Development

No branches or pull requests

3 participants