Erik Reider

Hmmm. I'm not sure about that one. A config option would be good though

File over name sounds like the best solution. Should we play a default sound of there is none specified? Maybe another config option?

The default sound file could get pretty messy so I'd stick with a configurable sound name as a fallback. As mentioned in another issue, I think that the spec includes...

https://github.com/ErikReider/SwayNotificationCenter/blob/0f69f080b40d3621069bfadea0a414ba2e96bb3a/src/notiModel/notiModel.vala#L154-L158 We should probably convert this into an enum :)

We should stick with the standardized categories and add some gnome / KDE specific ones too just to be safe

Hmmm. What about using the same error sound for all errors? Something like this ```vala case "network.error": case "something.error": // play error sound break; ```

That sounds like a good plan! But to future proof this I have a suggestion. Instead of specifying a sound, we could add a dict for sounds, images, icons, etc......

That looks really good. Makes it easier to add more features in the future if needed :)

This is due to the "click to close" functionality of the ControlCenter. ~What I can do is to disable click to close when the `GTK_DEBUG=interctive` variable is passed to swaync~

I might have misspoken... A large GTK window covers the whole screen to grab the clicks and I'm not sure if I'm able to pass those click events through to...