tristan/kdeconnect-kde
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kdeconnect-kde/plugins/virtualmonitor
History
Fabian Arndt bfdb1c7ff5 Virtual Monitor: always provide dbus path 
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?
2024-05-31 20:31:21 +00:00
..
CMakeLists.txt kdeconnect_add_plugin: Autogenerate logging category 2023-08-07 19:47:41 +02:00
kdeconnect_virtualmonitor.json virtualmonitor: implemented capabilities check 2024-05-30 23:13:54 +00:00
README Introduce the VirtualMonitor plugin 2022-05-25 00:04:47 +02:00
virtualmonitorplugin.cpp Virtual Monitor: always provide dbus path 2024-05-31 20:31:21 +00:00
virtualmonitorplugin.h virtualmonitor: implemented capabilities check 2024-05-30 23:13:54 +00:00

README 

This plugin will allow users to use other kde connect devices as external displays.

It will use krfb-virtualmonitor to create it and feed the information and also request an URL to be opened on the other device that should be rendering the contents.

Upon connection, we'll be notifying under kdeconnect.virtualmonitor about our "resolutions, which include objects with a "resolution" and a "scale". These will provide the information necessary to issue a remote feed.

When a virtual monitor is requested, kdeconnect.virtualmonitor.request will include a "url" field that contains all information necessary to connect to the created feed. The remote client needs to support this url type.