Python / C++ application D-Bus usage issues

[Thiago Macieira]

On sexta-feira, 14 de dezembro de 2012 19.04.24, Kip Warner wrote:
> > You do not need to get a proxy object. You simply need to send the signal.
> 
> I'm sorry, but I am very confused. Can you show me how this is suppose
> to work? My C++ application and Python application only need to send
> signals back and forth and do not need actual proxy objects. But the
> code I have written uses APIs that all seem to require proxy objects or
> interfaces.

I'm sorry, I don't know the API of the Python binding. I can't help you with 
it.

But since your C++ code does not reply to Introspection, you need to find a way 
to emit the signal in the Python side without creating a proxy object. Forget 
the C++ application for a minute: make the Python object emit and confirm that 
it got emitted by using dbus-monitor. Once that is working, go back to your 
C++ application.

> > Indeed, you are doing it.
> > 
> > But I don't think you've even reached that point. Your application stopped
> > earlier.
> 
> I checked with a Python print statement right before the signal is
> suppose to be fired off and it does reach that point.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel Open Source Technology Center
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/dbus/attachments/20121214/4d2e06e5/attachment.pgp>