Add a fast mode to Counter where more than one is skipped on long press #2215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Oftentimes I cannot be bothered to hold the + button of the timer down until 30s is reached, because it takes so long. Instead, I just set 30s less and wait around a bit after the timer rings.
When setting an alarm, I have the same problem with the minutes. It just takes too long.
This adds a 'fast mode' to the
Counter
widget that is used in these cases.An application designer can enable this for a widget and is then able to specify how many steps should be skipped on each trigger of the
LV_EVENT_LONG_PRESSED_REPEAT
event.This PR enables this with value 5 for
Timer
,Alarm
(minutes only) andSettingDateTime
(days and minutes only).Also includes a small fix for
Counter
where theValueChangedHandler
was not called ifSetValue
was used. I don't think there were any bugs caused by this yet, I checked all uses of the function.