Skip to content

Help about usage of add_signal_receiver #7

@gteti

Description

@gteti

Hello,
I'd like to have some help about the use of the function add_signal_receiver. I've read the documentation and seen the example provided here but I still can't quite get a correct signal reading.

Here's my code:

def catchall_hello_signals_handler(self, hello_string):
        print("Received a signal and it says: ", hello_string)

self.bus.add_signal_receiver(
                    self.catchall_hello_signals_handler,        
                    dbus_interface="com.mybus.DBus.Donald",    
                    signal_name="execCommandSent",              
                    path="/Donald"                             
                )

My bus name is com.mybus
The object is called Donald/
The interface under the object is com.mybus.DBus.Donald
The signal here is execCommandSent from which I want to ear what is says.

What I read in the qdbusviewer app when I connect to this signal is something like:
`Received signal from :1.10, path /Donald, interface com.mybus.DBus.Donald, member execCommandSent
Arguments: [Argument: a{sv} {"file_path0" = [Variant(QString): "/home/exports/upload/update.tgz"],"has_recovery_point" = [Variant(QString): "version@1.00_update@true"], "name" = [Variant(QString):"update_remote_prj"]}]

I'd like to read the same through my python code and interpret it. For now I've been able to read this through the method execCommand and not from the signal execCommandSent.

Can anyone help me? Thank you very much.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions