https://bugs.kde.org/show_bug.cgi?id=489463

--- Comment #4 from Alik Aslanyan <inli...@pm.me> ---
What happens in Polonium as is follows.

1) User maximizes the Window
2) Polonium while receiving maximizedChanged untilies the window, by removing
it from the tile
3) KWin ignores removed tile and reinserts it somewhere in the code.
4) Polonium receives TileChanged with non-NULL and freaks out

Previously it was as this
1) User maximizes the Window
2) Polonium while receiving maximizedChanged untilies the window, by removing
it from the tile
3) Polonium receives TileChanged with NULL

This is more correct description of the logic issue here. When script decides
to remove window from tile, script shouldn't put it again

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to