Giter Site home page Giter Site logo

Comments (2)

bkw777 avatar bkw777 commented on July 23, 2024

OK I think I have a solution for this. Still testing locally before pushing.

Basically, it's not necessarily a bug, but just the way it is, that the background monitor process to handle the button press only lives as long as the initial notification does.

I think it's good enough in this case to just override the default desktop timeout and tell the notification to expire one second before the next notification, and when closed or expired, to go away entirely and not appear in history.

So, when you get the notification, it stays up until you dismiss it, and while it's up, the button on it works.

And when you close it, it's cleared from history too, so there is no "broken" button sitting there in the notification history.

from mainline.

bkw777 avatar bkw777 commented on July 23, 2024

This was only about 10% bug and 90% not a bug in the first place but more a function of the particular desktop environment. I DID end up making a change to the notify-send.sh command line, which probably fixes it for most people. You can still get various forms of unwanted behavior, but it's mostly down to configuring your perticular desktop to do what you want.

The thing I can change here is I can specify that the notification should never expire on it's own from a timeout. That all by itself should make it "just work" for most people most of the time. It pops up, it sits there until you click it, and when you click it, it works. When you close it, it's gone and doesn't go into any history because you "saw" it and manually closed it.

Other details I can't change and they are going to be different for different desktops. One detail I had to do for my own case is, I'm using Lubuntu which uses LXQT desktop, which uses lxqt-notificationd to handle it's notifications. This particular app happens to have an option in it's advanced settings for it's history management that says "ignore these apps:". It means don't put any notifications from those apps into the history. So in my case, I want "mainline" in that option. This prevents the situation of ever seeing an old notification with a non-working button in it.

Everyone else's desktops will use various other apps to display and manage notifications and who knows what odd special options and features they each have?

So this is about as good as I think can be expected for now.

See the thread here for details:
vlevit/notify-send.sh#13

from mainline.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.