Phosphor
Qt6 / Wayland library suite for window-management tools
 
Loading...
Searching...
No Matches
Phosphor::Screens::ResolverEndpoint Struct Reference

D-Bus endpoint that ScreenResolver queries. More...

#include <phosphor-screens/include/PhosphorScreens/Resolver.h>

Public Attributes

QString service = QString(PhosphorProtocol::Service::Name)
 
QString path = QString(PhosphorProtocol::Service::ObjectPath)
 
QString interfaceName = QString(PhosphorProtocol::Service::Interface::Screen)
 
QString method = QStringLiteral("getEffectiveScreenAt")
 

Detailed Description

D-Bus endpoint that ScreenResolver queries.

Defaults match the PlasmaZones daemon's canonical org.plasmazones.Screen interface (sourced from PhosphorProtocol::Service::*). A consumer that runs against a different service overrides them per call.

Top-level (not nested in ScreenResolver) so its default member initialisers are usable as default-argument values on ScreenResolver::effectiveScreenAt — nested types' member initialisers are unreachable at the enclosing class's default-arg parse site.

interfaceName (not interface) sidesteps the Microsoft interface SDK macro that Qt's AUTOMOC pre-processor occasionally mishandles.

Member Data Documentation

◆ interfaceName

QString Phosphor::Screens::ResolverEndpoint::interfaceName = QString(PhosphorProtocol::Service::Interface::Screen)

◆ method

QString Phosphor::Screens::ResolverEndpoint::method = QStringLiteral("getEffectiveScreenAt")

◆ path

QString Phosphor::Screens::ResolverEndpoint::path = QString(PhosphorProtocol::Service::ObjectPath)

◆ service

QString Phosphor::Screens::ResolverEndpoint::service = QString(PhosphorProtocol::Service::Name)

The documentation for this struct was generated from the following file: