--001a114c810e2bb9c3054a9db883 Content-Type: text/plain; charset=UTF-8 Hey, On Thu, Mar 9, 2017 at 10:56 PM, Chris Holland wrote: > It seems the ActionInvoked and NotificationClosed signal isn't exposed > anywhere. > > The signals are defined here: > https://github.com/KDE/plasma-workspace/blob/master/ > dataengines/notifications/notificationsengine.h#L84 > > And the signals are called here: > https://github.com/KDE/plasma-workspace/blob/master/ > dataengines/notifications/notificationaction.cpp#L54 > > Would it be possible to expose that signal somewhere? > Those signals are relied back to you into your client side code, eg. if you use KNotification, then you can listen to those signals there. This obviously only works for notifications that you yourself have created, you cannot listen to those signals of all notifications, that's only for the client and the shell to know. Cheers -- Martin Klapetek --001a114c810e2bb9c3054a9db883 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hey,

O= n Thu, Mar 9, 2017 at 10:56 PM, Chris Holland <zrenfire@gmail.com>= wrote:

It seem= s the ActionInvoked and NotificationClosed signal isn't exposed anywher= e.

The signals are defined here:
https://github.com/KDE/plasma-workspace/blob/master/dataengine= s/notifications/notificationsengine.h#L84

And the signals are called here:
https://github.com/KDE/plasma-workspace/blob/master/dataengin= es/notifications/notificationaction.cpp#L54

Would it be possible to expose that signal somewhere?

=

Those signals are relied back to you into your

cli= ent side code, eg. if you use KNotification,

then you can listen = to those signals there.

This obviously only works for notificatio= ns that

you yourself have created, you cannot listen

to= those signals of all notifications, that's only

for the clie= nt and the shell to know.

Cheers

--

Martin Klapetek

--001a114c810e2bb9c3054a9db883--