-
Sebastian Kügler authored
We'd previously get a lot of changed events (for all the properties of outputdevice, for example), which all end up triggering the ConfigMonitor. Ideally, we only get one changed signal after the compositor is done. This patch achieves that by blocking configChanged() emission between config->apply() and config->applied() or config->failed(), and then triggers one configChanged() event and unblocks. We now get one changed signal from the configmonitor per atomic modesetting operation. Nice.
79acd5b5