Function stop() is counter-intuitive - need to add a pause() - or someting else #92

sofian · 2024-02-06T03:53:49Z

Exemple if you press Alarm stop() it should just get back to zero and stay there.
We had a similar problem with Chrono which ended with the following decision, which makes sense:

change behavior of stop() so it resets counter to zero
add a pause() function

See SofaPirate/Chrono#16

- Add a pause() function and change behavior of stop() (closes #92)

sofian added the enhancement label Feb 6, 2024

sofian self-assigned this Feb 6, 2024

sofian mentioned this issue Feb 6, 2024

Add options to reset generative sources #87

Closed

sofian changed the title ~~Function stop() is counter-intuitive - need to add a pause()~~ Function stop() is counter-intuitive - need to add a pause() - or someting else Feb 8, 2024

sofian mentioned this issue Feb 8, 2024

Introduce / include Chronometer class in documentation and/or as a Node #99

Closed

sofian mentioned this issue Apr 5, 2024

Define and implement time-related functions common oscillators and timing units #110

Open

sofian added a commit that referenced this issue Jan 4, 2025

Adjusted API of Chronometer (closes #92).

b686963

sofian added a commit that referenced this issue Jan 4, 2025

- Merge class Unit and Node (closes #106)

7bf92b6

- Add a pause() function and change behavior of stop() (closes #92)

sofian closed this as completed Jan 4, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Function stop() is counter-intuitive - need to add a pause() - or someting else #92

Function stop() is counter-intuitive - need to add a pause() - or someting else #92

sofian commented Feb 6, 2024

Function stop() is counter-intuitive - need to add a pause() - or someting else #92

Function stop() is counter-intuitive - need to add a pause() - or someting else #92

Comments

sofian commented Feb 6, 2024