Re: DBUS signals?

[Jussi Lahtinen <jussi.lahtinen@xxxxxxxxx>]

Benoit,
it seems using DBusSignal also messed up trayicon handling... middle button
clicks are not received anymore. And I get random crashes / hangs.
See attachment.


Jussi

On Thu, Sep 26, 2024 at 2:25 AM Jussi Lahtinen <jussi.lahtinen@xxxxxxxxx>
wrote:

> You'll need to tell it the object and the signal-name and set "every" to
>> true in the "new" parameter.
>>
> No, the signals have no destination, they are already for everyone. Also
> I'm not waiting for an object and the signal name is given in the event.
> See DBusSignal.
>
>
>> I'd give you better details but my system doesn't use Hal.Manager
>>
>> The IDE gives some dbus introspection in the bottom tabs (I forget
>> where).
>> qDBusViewer (available on your distro?) is a good utility to look at what
>> DBus is happening on your system.
>>
>> Signals are possibly the hardest way to learn about the dbus component
>> and dbus in general.
>>
>
> I did this:
> $ dbus-monitor --system >> signals.txt
>
> And immediately shutdown my computer. I got 1.1 MB of shit... oh wow. But
> there is also the PrepareForShutdown signal, but I cannot see that in
> Gambas.
> "signal time=1727305608.503257 sender=:1.11 -> destination=(null
> destination) serial=109 path=/org/freedesktop/login1;
> interface=org.freedesktop.login1.Manager; member=PrepareForShutdown"
>
> Benoit, any reason why this is missing? Is something related to DBus
> closed already..?
> Is there another Qt/GTK independent way to detect shutdown?
>
>
> Jussi
>
>

Attachment: GAlarm-0.7.46.tar.gz
Description: application/gzip