Zander671/river
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

View: fix unmap/destroy control flow

Browse Source 
Currently the view destruction sequence is started as soon as a view
is unmapped. However, this is incorrect as a client may map the view
again instead of destroying it.

Instead, only start the view destruction sequence when the underlying
xdg toplevel or xwayland surface is destroyed.
This commit is contained in:
Isaac Freund
2021-10-02 14:29:39 +02:00
parent e0784247b6
commit 9270a2df08
12 changed files with 65 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
river/Root.zig
View File

@ -291,7 +291,7 @@ pub fn startTransaction(self: *Self) void {
while (view_it) |view_node| : (view_it = view_node.next) {
const view = &view_node.view;
if (view.destroying) continue;
if (view.surface == null) continue;
if (view.shouldTrackConfigure()) {
// Clear the serial in case this transaction is interrupting a prior one.
@ -386,10 +386,13 @@ fn commitTransaction(self: *Self) void {
const view = &view_node.view;
view_it = view_node.next;
if (view.destroying) {
view.destroy();
if (view.surface == null) {
view.dropSavedBuffers();
view.output.views.remove(view_node);
if (view.destroying) view.destroy();
continue;
}
assert(!view.destroying);
if (view.pending_serial != null and !view.shouldTrackConfigure()) continue;