[WIP] Add vicious.change_timer: a helper to change the timeout #62
Conversation
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
blueyed
changed the title
blueyed
force-pushed
the
add-change-timer
branch
from
0d91a6e to
50dc101
Compare
This is useful in case you want to change the timeout value for a registered widget, e.g. from the format callback function. I am using this to have a shorter timeout interval for the temperature widget when its value is above some threshold. Signed-off-by: Daniel Hahler <[email protected]>
blueyed
force-pushed
the
add-change-timer
branch
from
50dc101 to
f25866f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is useful in case you want to change the timeout value for a
registered widget, e.g. from the format callback function.
I am using this to have a shorter timeout interval for the temperature
widget when its value is above some threshold.
TODO:
It appears to trigger some internal weird issue when enter/leave is triggered for tooltips (already undefined function in the callback or something similar?!)