afb81b8278
Some checks failed
Docker. / Ubuntu (push) Has been cancelled
User-agent updater. / User-agent (push) Failing after 15s
Lock Threads / lock (push) Failing after 10s
Waiting for answer. / waiting-for-answer (push) Failing after 22s
Needs user action. / needs-user-action (push) Failing after 8s
Can't reproduce. / cant-reproduce (push) Failing after 8s
Close stale issues and PRs / stale (push) Has been cancelled
19 lines
957 B
ReStructuredText
19 lines
957 B
ReStructuredText
Window Identifiers
|
|
==================
|
|
|
|
Most portals interact with the user by showing dialogs. These dialogs should
|
|
generally be placed on top of the application window that triggered them. To
|
|
arrange this, the compositor needs to know about the application window. Many
|
|
portal requests expect a ``"parent_window"`` string argument for this reason.
|
|
|
|
Under X11, the ``"parent_window"`` argument should have the form ``x11:<XID>``,
|
|
where ``<XID>`` is the XID of the application window in hexadecimal notation.
|
|
For example, ``x11:1234``.
|
|
|
|
Under Wayland, it should have the form ``wayland:<HANDLE>``, where ``<HANDLE>``
|
|
is a surface handle obtained with the `xdg_foreign
|
|
<https://gitlab.freedesktop.org/wayland/wayland-protocols/-/blob/main/unstable/xdg-foreign/xdg-foreign-unstable-v2.xml>`_
|
|
protocol. For example, ``wayland:~12l9jdl.-a``.
|
|
|
|
For other windowing systems, or if you don't have a suitable handle, just pass
|
|
an empty string for ``"parent_window"``. |