Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ XMapSubwindows(3X) — A/UX 3.0.1

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

XChangeWindowAttributes(3X)

XConfigureWindow(3X)

XCreateWindow(3X)

XDestroyWindow(3X)

XRaiseWindow(3X)

XUnmapWindow(3X)




XMapWindow(3X) XMapWindow(3X)
NAME XMapWindow, XMapRaised, XMapSubwindows - map windows SYNOPSIS XMapWindow (display, w) Display *display; Window w; XMapRaised (display, w) Display *display; Window w; XMapSubwindows (display, w) Display *display; Window w; DESCRIPTION The XMapWindow function maps the window and all of its subwindows that have had map requests. Mapping a window that has an unmapped ancestor does not display the window but marks it as eligible for display when the ancestor be- comes mapped. Such a window is called unviewable. When all its ancestors are mapped, the window becomes viewable and will be visible on the screen if it is not obscured by another window. This function has no effect if the window is already mapped. If the override-redirect of the window is FALSE and if some other client has selected SubstructureRedirectMask on the parent window, the X server generates a MapRequest event, and the XMapWindow function does not map the window. Other- wise, the window is mapped, and the X server generates a MapNotify event. If the window becomes viewable and no earlier contents for it are remembered, the X server tiles the window with its background. If the window's background is undefined, the existing screen contents are not altered, and the X server generates zero or more Expose events. If backing-store was maintained while the window was unmapped, no Expose events are generated. If backing-store will now be maintained, a full-window exposure is always generated. Otherwise, only visible regions may be reported. Similar tiling and exposure take place for any newly viewable inferiors. If the window is an InputOutput window, XMapWindow generates Expose events on each InputOutput window that it causes to be displayed. If the client maps and paints the window and if the client begins processing events, the window is paint- ed twice. To avoid this, first ask for Expose events and then map the window, so the client processes input events as November, 1990 1



XMapWindow(3X) XMapWindow(3X)
usual. The event list will include Expose for each window that has appeared on the screen. The client's normal response to an Expose event should be to repaint the window. This method usually leads to simpler programs and to proper interaction with window managers. The XMapRaised function maps the window and all associated subwindows which have had map requests and raises the speci- fied window to the top of the stack. The XMapSubwindows function maps all subwindows for a speci- fied window in top-to-bottom stacking order. The X server generates an Expose event on each newly displayed window. This may be much more efficient than mapping many windows one at a time because the server needs to perform much of the work only once, for all the windows, rather than for each window. Arguments These functions accept the following arguments: display Specifies the connection to the X server. w Specifies the window ID. ERRORS BadWindow A value for a Window argument does not name a de- fined window. The XMapWindow, BadWindow, and XMapSubwindows functions can generate a BadWindow error. SEE ALSO XChangeWindowAttributes(3X), XConfigureWindow(3X), XCreateWindow(3X), XDestroyWindow(3X), XRaiseWindow(3X), XUnmapWindow(3X)
Xlib - C Language Interface
2 November, 1990

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026