Skip to content

patch: dynamically updated the displayed notification#25

Open
TAAPArthur wants to merge 2 commits intodudik:masterfrom
TAAPArthur:dynamic_updates
Open

patch: dynamically updated the displayed notification#25
TAAPArthur wants to merge 2 commits intodudik:masterfrom
TAAPArthur:dynamic_updates

Conversation

@TAAPArthur
Copy link
Copy Markdown

Notifications can now have an id and if a notification is already being displayed with that id, instead of creating a new notification, the message displayed will be updated. The implementation is based on message queues.

Depends on #24

Moved the code to parse lines into its own method to make it easier to
reuse for patches and less likely to cause conflicts.

Also imports were sorted.
Notifications can now have an id and if a notification is already being
displayed with that id, instead of creating a new notification, the
message displayed will be updated. The implementation is based on
message queues.
@dudik dudik added the patch This pull request is a patch label Mar 15, 2021
@vv52
Copy link
Copy Markdown

vv52 commented Mar 20, 2022

How is the message id set in practical use? I've compiled herbe with this port and looked through the C code. I don't see any way to set HERBE_ID with an arg. I've tried running multiple herbe calls from the same process or script and they still queue instead of updating. I might be missing something obvious here but I think basic documentation of this feature would be helpful. Thank you!

PS just wanted to say thank you for your work on this patch, regardless of my ability to intuit it's implementation

@TAAPArthur
Copy link
Copy Markdown
Author

@vv52 I don't actually use herbe anymore, but I believe I let the id be set with the env var HERBE_ID.

tunalad added a commit to tunalad/herbe that referenced this pull request Apr 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

patch This pull request is a patch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants