<table><tr><td style="">dvratil added a comment.
</td><a style="text-decoration: none; padding: 4px 8px; margin: 0 8px 8px; float: right; color: #464C5C; font-weight: bold; border-radius: 3px; background-color: #F7F7F9; background-image: linear-gradient(to bottom,#fff,#f1f0f1); display: inline-block; border: 1px solid rgba(71,87,120,.2);" href="https://phabricator.kde.org/D9904" rel="noreferrer">View Revision</a></tr></table><br /><div><div><p>Indeed for out-of-process backends the config arrives serialized via DBus and a new copy which is then passed to a client is created during serialization.</p>
<p>The change you mention is likely unrelated - it only mentions X11 which is always out-of-process, so not affected by this change, and does not look very sensible to me (if just because ConfigMonitor only holds weak references to Configs so by changing m_currentConfig there's a high chance the original config will be destroyed anyway).</p></div></div><br /><div><strong>REPOSITORY</strong><div><div>R110 KScreen Library</div></div></div><br /><div><strong>REVISION DETAIL</strong><div><a href="https://phabricator.kde.org/D9904" rel="noreferrer">https://phabricator.kde.org/D9904</a></div></div><br /><div><strong>To: </strong>dvratil, sebas, davidedmundson<br /><strong>Cc: </strong>plasma-devel, ZrenBot, progwolff, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart<br /></div>