xnest/man/Xnest.man

71 to synchronize its window and graphics operations with the real server.
86 by default maintains the same top-level window and the same real server
88 If the user selects full regeneration, even the top-level window and the
150 window.
154 This window corresponds to the root window of the nested server.
162 window.
164 will allow the user to make any top-level window smaller, but it will not
165 actually change the size of the nested server root window.
168 of the root window.
175 to be 3/4ths the dimensions of the root window of the real server.
180 window.
189 window as
197 will create a separate top-level window.
213 to do its own color map installation by bypassing the real window manager.
215 real window manager.
218 will keep the nested client window whose color map should be installed in the
223 window.
224 If this color map is of the same visual type as the root window of the nested
229 window as well.
230 Since this does not have to be the case, window managers should look primarily
235 window.
237 Unfortunately, window managers are not very good at doing that yet so this
245 as the root window instead of creating a window.
293 It is a rather demanding client, however, since almost any window or graphics
294 request from a nested client will result in a window or graphics request from
313 window of the
319 window, unless the real server has support for more than one installed color map
321 The color map associated with the top window of the
328 will put the top window of this nested client and all other top windows of the
333 window on the real server.
334 Thus, it is important that the real window manager that manages the
336 top-level window looks at the
340 window.
341 Since most window managers don't yet appear to implement this convention
345 bypassing the real window manager.
347 the real window manager since it will interfere with the