cbbd684430
Begin of proper multiscreen support! We load configuration sets for the connected outputs. Each set of screens represents a unique configuration. For that we use the md5 sum of the edid+connector as uuid of an output. Each of the md5 sums is then used to create a uuid of the output set. We can be quite certain that this will generate unique ids for the use cases we will face. The uuids are used as group names. And from there we read the global position. The uuids are considered internal information. It is not intended for users to configure manually in the config file. The intended way to configure will be the OutputManagementInterface which recently got added to KWayland. Once KWin applies a configuration it will store it to config so that it can be loaded on next startup. The configuration looks like: [DrmOutputs][abcdef0123][0123abcdef] Position=0,0 [DrmOutputs][abcdef0123][fbca3bcdef] Position=1280,0 This is an example for two outputs set next to each other. Reviewed-By: Sebastian Kügler |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| drm.json | ||
| drm_backend.cpp | ||
| drm_backend.h | ||
| egl_gbm_backend.cpp | ||
| egl_gbm_backend.h | ||
| logging.cpp | ||
| logging.h | ||
| scene_qpainter_drm_backend.cpp | ||
| scene_qpainter_drm_backend.h | ||
| screens_drm.cpp | ||
| screens_drm.h | ||