D15150: [wayland] Asyncronously update maximise flags

davidedmundson added a comment.


  > clientMaximizedStateChanged is now called on ShellClients. Before it was only called on Clients in geometry.cpp. It's not mentioned in the Summary. Is this change intended?
  
  It was called in AbstractClient::setMaximize  which affects both ShellClients and Clients.
  
  With this patch on wayland that does nothing because the state hasn't changed before and after the virtual changeMaximize doesn't change. So we still get the same amount when we have an async update.
  
  I would move those signals into Client:changeMaximize for consistency, but that's called directly in a few places and it would introduce an X behavioural change (though probably a safe one)

REPOSITORY
  R108 KWin

REVISION DETAIL
  https://phabricator.kde.org/D15150

To: davidedmundson, #kwin
Cc: romangg, zzag, kwin, mkulinski, ragreen, jackyalcine, Pitel, iodelay, bwowk, ZrenBot, lesliezhai, ali-mohamed, hardening, jensreuterberg, abetts, sebas, apol, mart