Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(372)

Unified Diff: ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h

Issue 2329323002: Avoid blocking while mapping an X11 window (Closed)
Patch Set: Created 4 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h
diff --git a/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h b/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h
index 40933bc596479e6cd9e5a73b8fbe066ef83882fe..3096e7d741b67859552e4bc59be7b597e7938b52 100644
--- a/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h
+++ b/ui/views/widget/desktop_aura/desktop_window_tree_host_x11.h
@@ -278,6 +278,11 @@ class VIEWS_EXPORT DesktopWindowTreeHostX11
// Is the window mapped to the screen?
bool window_mapped_;
+ // If |wait_for_map_| is true, it means we called MapWindow, but haven't yet
+ // gotten the MapNotify event yet. We use this as part of the calculation for
+ // whether the window is "visible".
+ bool wait_for_map_;
Tom (Use chromium acct) 2016/09/12 22:45:07 Since this cl means we don't wait for maps anymore
dackerman 2016/09/23 14:12:37 How about |is_waiting_for_map_|, |expecting_map_no
Tom (Use chromium acct) 2016/09/23 18:35:48 It does make sense to add the check for wait_for_m
dackerman 2016/09/25 19:45:36 Done.
+
// Should we wait for an UnmapNotify before trying to remap the window?
// If |wait_for_unmap_| is true, we have sent an XUnmapWindow request to the
// server and have yet to receive an UnmapNotify.

Powered by Google App Engine
This is Rietveld 408576698