Hi,
I'm using QT5.3 and I've the same problem with multiple 'out' parameters in
qdbusxml2cpp, that I just found in this mail list but I don't understand
the solution.
So,
My XML file is:
http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd";>
On sexta-feira, 26 de julho de 2013 16:35:24, Matt Hoosier wrote:
> Okay, I agree that I could pin down the parent class name and get automatic
> dispatch wired up. But I'd like to understand why the normal
> QMetaObject::invokeMethod() dispatch isn't allowed in this case (that is,
> more than one
Hi Thiago,
Thanks for replying. I'd traced through the logic in qdbusxml2cpp's source
as well before posting, and saw the same chunk of logic that determines
whether to emit only the placeholder.
Okay, I agree that I could pin down the parent class name and get automatic
dispatch wired up. But I'
On sexta-feira, 26 de julho de 2013 15:27:21, Matt Hoosier wrote:
> I've observed that qdbusxml2cpp doesn't emit the QMetaCall that would
> forward a D-Bus method-call message from the adaptor along to the "business
> logic" class that provides slots to implement all the various methods.
> E.g., if
I've observed that qdbusxml2cpp doesn't emit the QMetaCall that would
forward a D-Bus method-call message from the adaptor along to the "business
logic" class that provides slots to implement all the various methods.
E.g., if I have:
the adaptor code for this method ends up l
