Implement updating of notifications

This commit is contained in:
Kovid Goyal
2024-07-28 12:25:35 +05:30
parent 59c175f312
commit 2bffea2bdc
9 changed files with 96 additions and 54 deletions

View File

@@ -127,7 +127,9 @@ escape code to inform when the notification is closed::
If no notification id was specified ``i=0`` will be used.
If ``a=report`` is specified and the notification is activated/clicked on
then both the activation report and close notification are sent.
then both the activation report and close notification are sent. If the notification
is updated then the close event is not sent unless the updated notification
also requests a close notification.
.. note:: On macOS the OS does not supply notification
closed events to applications. As such close events must be implemented
@@ -137,11 +139,19 @@ then both the activation report and close notification are sent.
being authoritative.
Closing an existing notification
----------------------------------
Updating or closing an existing notification
----------------------------------------------
.. versionadded:: 0.36.0
The ability to close a previous notification was added in kitty 0.36.0
The ability to update and close a previous notification was added in kitty 0.36.0
To update a previous notification simply send a new notification with the same
*notification id* (``i`` key) as the one you want to update. If the original
notification is still displayed it will be replaced, otherwise a new
notification is displayed. This can be used, for example, to show progress of
an operation. Note that how smoothly the existing notification is replaced
depends on the underlying OS, for example, on Linux the replacement is usually flicker
free, on macOS it isn't, because of Apple's design choices.
To close a previous notification, send::