> Hmmm. That's a fair point, but it's a change that we don't advertise at > the protocol level. There are occasions where that happens and we > haven't audited all apps that do it for "good reasons". I recommend to > keep it as is for this release. And next time, return an error to > indicate more clearly that the call failed, because we're not supporting > the call anymore.
Pushed a compromise as rev 401. stack_close_notification_handler() acts upon invocation again, but leaves the notification-queue in Stack untouched. I also added a warning when we get an id == 0 from DBus. -- https://code.edge.launchpad.net/~macslow/notify-osd/fix-427924/+merge/12281 Your team ayatana-commits is subscribed to branch lp:notify-osd. _______________________________________________ Mailing list: https://launchpad.net/~ayatana-commits Post to : [email protected] Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
