tristan/kdeconnect-kde
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Virtual Monitor: always provide dbus path

Browse source 
The plugin should always be loaded, as:
- we can provide a virtual display over VNC, even if the device isn't capable to use virtual displays itself (`krfb-virtualmonitor`)
- we would do the capabilities check regardless, if !670 gets merged
- hiding the DBus path doesn't trigger the `PluginChecker.qml` to think the plugin is unavailable, it just doesn't work
- -> is this a bug or intended behaviour?
This commit is contained in:
Fabian Arndt 2024-05-31 20:31:21 +00:00
parent a2c2c310fa
commit bfdb1c7ff5
1 changed files with 0 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
plugins/virtualmonitor/virtualmonitorplugin.cpp
View file

@ -119,10 +119,6 @@ void VirtualMonitorPlugin::receivePacket(const NetworkPacket &received)
QString VirtualMonitorPlugin::dbusPath() const QString VirtualMonitorPlugin::dbusPath() const
{ {
// Don't offer the feature if krfb-virtualmonitor is not around
if (!m_capabilitiesLocal.virtualMonitor)
return {};
return QLatin1String("/modules/kdeconnect/devices/%1/virtualmonitor").arg(device()->id()); return QLatin1String("/modules/kdeconnect/devices/%1/virtualmonitor").arg(device()->id());
} }