volume-notification-dunst VS mako

U could use a notifying client with a script. You could do that with dunst and this script.

So, using this github issue as a reference, I'm trying to make a wofi menu that appears when a bluetooth file transmission is sent to my PC from my phone (or any other device for that matter).

I currently use mako for the notifications. When I play Strategy Games (Mouse is all over the place) and a notifcation pops up, the mouse gets stuck on the notification message until I click it.

I use avizo as a volume indicator, mako for notifications generally.

I guess some standard notifications app like https://github.com/emersion/mako doesn't suffice, as it isn't related to a window?

mako is a Wayland notification daemon from one of the principal Sway/wlroots devs, and is currently provided with openSUSEway. It's pretty minimalist, but so are most things in the Sway/wlroots ecosystem.

It's a notification, I use mako: https://github.com/emersion/mako

Notifications: mako

Is there any way to force dbus to use a specific notification daemon? On one of my systems, I run both Plasma and Sway. The latter obviously doesn't have a notification system, so I'm using mako. As far as I can tell, mako automatically launches when a notification is fired, however this causes an issue with Plasma. Plasma seems to be shutting down its own notification daemon in favor of anything else that's running, and I'm not sure if there's a way to prevent it from doing that

I don’t use Thunderbird, but does it support using FreeDesktop notifications e.g. that would work with Mako? Some applications will fall back to their own windows if there’s no notification daemon running.