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
I am working on adding the option to choose a specific sound for the missed reading alert.
Currently, the same sound is used for fast falling and rising alerts. It is good to know which alert it is just by the sound of it.
This has been requested multiple times over the years: #555
@jamorham
I would like to make sure that the user will not have any unexpected surprises.
The way I can think of doing this is by adding two new preferences.
One will tell me that the user has changed the other alert's sound. In which case, only once upon update, the other alert's sound will be copied to be the the missed reading alert sound.
The other new preference will tell me if the user is attempting to change their other alert sound for the first time after an update.
In this case, he/she will see a silent notification telling them that the change they have made will have no impact on the missed reading alert and if they need to change that, they have to do it on the missed reading alert page.
This will cost us two new preferences just to accomplish this.
Is it worth it? Is it necessary?
Or, can I just announce it when it is released and inform everyone what to expect and not add the two new preferences?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am working on adding the option to choose a specific sound for the missed reading alert.

Currently, the same sound is used for fast falling and rising alerts. It is good to know which alert it is just by the sound of it.
This has been requested multiple times over the years:
#555
@jamorham
I would like to make sure that the user will not have any unexpected surprises.
The way I can think of doing this is by adding two new preferences.
One will tell me that the user has changed the other alert's sound. In which case, only once upon update, the other alert's sound will be copied to be the the missed reading alert sound.
The other new preference will tell me if the user is attempting to change their other alert sound for the first time after an update.
In this case, he/she will see a silent notification telling them that the change they have made will have no impact on the missed reading alert and if they need to change that, they have to do it on the missed reading alert page.
This will cost us two new preferences just to accomplish this.
Is it worth it? Is it necessary?
Or, can I just announce it when it is released and inform everyone what to expect and not add the two new preferences?
Beta Was this translation helpful? Give feedback.
All reactions