diff options
| author | Ilia Bozhinov <ammen99@gmail.com> | 2020-02-18 12:30:05 +0100 |
|---|---|---|
| committer | Simon Ser <contact@emersion.fr> | 2020-02-19 11:40:23 +0100 |
| commit | f416efa918702156fbc617bf32ca943c909e18ee (patch) | |
| tree | f1c4b44788d128daf85338d71f72b3129525d5de /backend | |
| parent | 7e990a6bdf160cf6888719eb3148096ad00ace7e (diff) | |
output-management: add current_configuration_dirty
Previously, if the current configuration contains an output X which is
destroyed, its head is automatically removed. If the compositor submits
the new configuration after X was removed, the current output
configuration is incorrectly detected to be the same as the previous
one, and no done event is sent. To prevent this, we can just keep track
of whether the current configuration is dirty, i.e whether we have sent
a done event for it.
Diffstat (limited to 'backend')
0 files changed, 0 insertions, 0 deletions