QDBus#

The QDBus namespace contains miscellaneous identifiers used throughout the Qt D-Bus module. More…

Note

This documentation may contain snippets that were automatically translated from C++ to Python. We always welcome contributions to the snippet translation. If you see an issue with the translation, you can also let us know by creating a ticket on https:/bugreports.qt.io/projects/PYSIDE

Detailed Description#

PySide6.QtDBus.QDBus.CallMode#

This enum describes the various ways of placing a function call. The valid modes are:

Constant

Description

QDBus.NoBlock

Place the call but don’t wait for the reply (the reply’s contents will be discarded).

QDBus.Block

Don’t use an event loop to wait for a reply, but instead block on network operations while waiting. This means the user-interface may not be updated until the function returns.

QDBus.BlockWithGui

Use the Qt event loop to wait for a reply. This means that the user-interface will stay responsive (processing input events), but it also means other events may happen, like signal delivery and other D-Bus method calls.

QDBus.AutoDetect

Automatically detect if the called function has a reply.

Constant	Description
QDBus.NoBlock	Place the call but don’t wait for the reply (the reply’s contents will be discarded).
QDBus.Block	Don’t use an event loop to wait for a reply, but instead block on network operations while waiting. This means the user-interface may not be updated until the function returns.
QDBus.BlockWithGui	Use the Qt event loop to wait for a reply. This means that the user-interface will stay responsive (processing input events), but it also means other events may happen, like signal delivery and other D-Bus method calls.
QDBus.AutoDetect	Automatically detect if the called function has a reply.

When using BlockWithGui, applications must be prepared for reentrancy in any function.