From: Bastian Krause <bst@pengutronix.de>
To: "Stahl, Michael" <mstahl@moba.de>,
"RAUC@pengutronix.de" <RAUC@pengutronix.de>
Cc: "Wolk, Steffen" <s.wolk@julabo.com>
Subject: Re: [RAUC] D-Bus control Qt
Date: Mon, 2 Aug 2021 10:14:49 +0200 [thread overview]
Message-ID: <9296676f-1bc0-e06e-840d-5b006c7876a6@pengutronix.de> (raw)
In-Reply-To: <AM9PR09MB47567FC83E0FE16AEC4BB2F0DBEF9@AM9PR09MB4756.eurprd09.prod.outlook.com>
Hi,
On 8/2/21 8:15 AM, Stahl, Michael wrote:
> Is there someone who implemented the DBus Property "Progress" into a
> Qt-Application? The problem seems the return value isi (Integer, String,
> Integer).
> For all other properties with a single return value like "Operation" or
> "LastError" the Qt DBus API works fine.
> I found an email from 28.Oct 2019 in the mailing list where Bastian
> Krause had the same issue. The answer was only that he had to cunsult
> the Qt DBus documentation on how a tuple is mapped to Qt types.
I just answered the mail by Steffen Wolk back then.
> Thats a good hint but after hours of searching the web I didn't find a
> solution. The return value for a property is QVariant in Qt.
>
> Trial 1 -> Read value by iface.property("Progress"):
> This is the error message I got when I try to read the progress property:
> Cannot construct placeholder type QDBusRawType
>
> Trial 2 -> Read value by iface.call("Get",...):
> Not able to get any information. The arguments of the returned
> QDBusMessages are always empty!
I don't have any experience here. Maybe Steffen Wolk (in cc) can share
how his solution looks like?
Regards,
Bastian
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
RAUC mailing list
next prev parent reply other threads:[~2021-08-02 8:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 6:15 Stahl, Michael
2021-08-02 8:14 ` Bastian Krause [this message]
2021-08-02 8:53 ` Wolk, Steffen
2021-08-02 11:41 ` [RAUC] Antwort: " Eugen.Wiens
2021-08-02 12:45 ` Stahl, Michael
2021-08-02 13:20 ` Stahl, Michael
2021-08-02 13:36 ` [RAUC] Antwort: " Eugen.Wiens
2021-08-02 14:29 ` Stahl, Michael
2021-08-02 14:53 ` [RAUC] Antwort: " Eugen.Wiens
2021-08-03 6:21 ` Stahl, Michael
2021-08-03 6:27 ` [RAUC] Antwort: " Eugen.Wiens
2021-08-03 8:27 ` Stahl, Michael
2021-08-03 10:57 ` Stahl, Michael
2021-08-03 11:00 ` Stahl, Michael
2021-08-03 11:14 ` [RAUC] Antwort: " Eugen.Wiens
2021-08-03 13:27 ` Stahl, Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9296676f-1bc0-e06e-840d-5b006c7876a6@pengutronix.de \
--to=bst@pengutronix.de \
--cc=RAUC@pengutronix.de \
--cc=mstahl@moba.de \
--cc=s.wolk@julabo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox