-
Notifications
You must be signed in to change notification settings - Fork 1
Closed
Description
Currently, actions are only defined but unimplemented in the async block.
python-sdbus-notifications/sdbus_async/notifications/__init__.py
Lines 112 to 121 in 7932225
| @dbus_signal_async() | |
| def action_invoked(self) -> Tuple[int, int]: | |
| """Signal when user invokes one of the actions specified. | |
| First element of tuple is notification id. | |
| Second element is the index of the action invoked. \ | |
| Matches the index of passed list of actions. | |
| """ | |
| raise NotImplementedError |
They are also named automatically by index, it would be nicer if they were able to be named properly via a string.
The blocking version for action receiving could simply block and return a tuple with both the ID and the actions upon expiry of the notification.
It would perhaps be best if this was made optional in the notify() function, as I imagine not everyone would want to block.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels