Save clock tool's last used time preference#3405
Open
dev-shady wants to merge 5 commits into
Open
Conversation
…ich re-renders the ui
Author
|
@veloce need your review and inputs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #3394
Note: There are two separate ingresses (inputs) for time change for the two clocks and one ingress for common change. Check attached video for clarity . But right now I have only kept a single field to drive default values of both through it. Meaning you can change one clock to be say 10 mins and other clock to be 5 mins and play but right now, only the last updated value will be used as the default value. We can keep separate defaults for the two clocks as well but need confirmation on the UX before doing it.
Video:
Recording_2026-06-29-08-47-53_1.mp4