https://bugs.kde.org/show_bug.cgi?id=452780
--- Comment #3 from David Edmundson <k...@davidedmundson.co.uk> --- I see your point. Though I don't want to introduce a two properties on each client which are maybe in sync maybe not and still have it still awkwardly racey. What I think we would want is: - API to write directly to Compositor::suspend/resume (exposed somehow) - API to set a flag (maybe generic transient config writing) to disable whether updateClientCompositeBlocking does anything Then your script would: - disable updateClientCompositeBlocking from doing anything so your script takes over control - monitor clients - call suspend/disable as appropriate Though in your examples one could also just use Window rules? -- You are receiving this mail because: You are watching all bug changes.
