From: Christian Hergert <christian@sourceandstack.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: Chengyang Zhu <colazcyg@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH RFC v3 1/1] ui/dbus: add org.qemu.Display1.UIInfo interface
Date: Wed, 19 Aug 2026 16:50:10 +0200 [thread overview]
Message-ID: <b9e15e18-a92c-4835-8d8b-b27722e14003@sourceandstack.com> (raw)
In-Reply-To: <CAJ+F1CL8kFYjgU-yU67kX2oX9PEapzz301RmW0=dPtnkffN-0Q@mail.gmail.com>
On 8/19/26 4:43 PM, Marc-André Lureau wrote:
> That was his v1. But then we would need to have a way to introspect
> the known keys, and this is not really binding/tools friendly.
I would think that getting the current values is essentially the answer
to what keys are supported? If you use a `mv` with a nullable you can
export all the known keys and their values.
But ...
> Maybe we can have a lock on the interface? that would be per
> connection, but it could be enough?
I'm okay with the idea of exporting properties for all the things. I'm
also okay with them being read/write. I just think they should apply
immediately if using that API.
And if you want to set all of them "atomically", use either an extended
SetUIInfo variant (either more parameters or a vardict).
Anyway, just my 2 cents.
-- Christian
prev parent reply other threads:[~2026-08-19 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 13:45 [PATCH RFC v3 0/1] the org.qemu.Display1.UIInfo interface design Chengyang Zhu
2026-08-18 13:45 ` [PATCH RFC v3 1/1] ui/dbus: add org.qemu.Display1.UIInfo interface Chengyang Zhu
2026-08-18 15:01 ` Marc-André Lureau
2026-08-19 14:39 ` Christian Hergert
2026-08-19 14:43 ` Marc-André Lureau
2026-08-19 14:50 ` Christian Hergert [this message]
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=b9e15e18-a92c-4835-8d8b-b27722e14003@sourceandstack.com \
--to=christian@sourceandstack.com \
--cc=colazcyg@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
/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