Wayland output is on protocol level and not dependent on the hardware
platform. Next steps are to do the same for output device and then let
the virtual output call into these initializing functions as well.
Details
Details
- Reviewers
davidedmundson - Group Reviewers
KWin - Maniphest Tasks
- T10016: Improve Wayland zero output handling
- Commits
- R108:21aee588af39: Initialize Wayland output in AbstractOutput
Manually and auto test.
Diff Detail
Diff Detail
- Repository
- R108 KWin
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
Note, that there are still some properties in DrmOutput for which we still need initDrmWaylandOutput. Hopefully goes away in a few patches though.
Comment Actions
Note, that there are still some properties in DrmOutput for which we still need initDrmWaylandOutput. Hopefully goes away in a few patches though.
Ack, it's in a bit of a messy state. But no worse than the current one.
abstract_output.cpp | ||
---|---|---|
135 | this does nothing, I think setWaylandOutput can be killed completely | |
141 | 2 newlines |