DMXGetWindowAttributes(3x)

1DMXGetWindowAttributes(3X)                          DMXGetWindowAttributes(3X)
2
3
4

NAME

6       DMXGetWindowAttributes - determine back-end window attributes
7

SYNOPSIS

9       #include <X11/extensions/dmxext.h>
10
11       Bool DMXGetWindowAttributes(Display *dpy,
12                                   Window window,
13                                   int *screen_count,
14                                   int available_count,
15                                   DMXWindowAttributes *attr);
16

DESCRIPTION

18       When  calling  DMXGetWindowAttributes(), window specifies the window ID
19       of a window on the Xdmx(1) server  and  available_count  specifies  the
20       length of attr.
21
22       The  number  of  screens  for  which  information  is available will be
23       returned in screen_count and information about  those  screen  will  be
24       returned  in  attr.  If screen_count is less than available_count, then
25       information for all of the screens will be returned.  Otherwise, infor‐
26       mation for the first available_count screens will be returned.
27
28       The DMXWindowAttributes structure is:
29
30       typedef struct {
31           int          screen;
32           Window       window;
33           XRectangle   pos, vis;
34       } DMXWindowAttributes;
35
36       For  each  back-end  X  server  that displays a portion of window, this
37       structure contains the physical screen  containing  that  portion,  the
38       window  ID  on the back-end X server of the window containing that por‐
39       tion, the position and dimensions of the window on the  back-end  (pos,
40       in screen coordinates), and the visible area of the window on the back-
41       end (vis, in window-relative coordinates -- all zeros if the window  is
42       not visible on the backend).
43
44       To   obtain   more  information  about  the  physical  screen  use  the
45       DMXGetScreenAttributes(3X) call.
46
47       Note that DMX allows multiple back-end windows to overlap in their view
48       of  the DMX logical window.  Further, a logical window does not have to
49       be completely covered by back-end windows -- there may be gaps.
50
51       As an example, consider  a  500x500  window  that  spans  the  top  two
52       1024x768  back-end  displays  (A and B) of a 2048x1536 DMX display com‐
53       posed of 4 1024x768 back-end displays arranged in a cube:
54
55           A B
56           C D
57
58       In this case, the DMXGetWindowAttributes call would return the  follow‐
59       ing information for the 500x500 window:
60
61       display A: 500x500 window at 1024-250,0 (relative to back end)
62                  with 250x500 visible at 0,0 (relative to window origin)
63
64       display B: 500x500 window at -250,0 (relative to back end)
65                  with 250x500 visible at 250,0 (relative to window origin)
66
67       display C: 500x500 window at 1024-250,-768 with 0x0 visible at 0,0
68
69       display D: 500x500 window at -250,-768 with 0x0 visible at 0,0
70

RETURN VALUE

72       DMXGetWindowAttributes() returns True unless there is a protocol error.
73
74       DMXGetWindowAttributes() can generate BadWindow and BadAlloc errors.
75

NOTES

77       Because this call transports a great deal of information over the wire,
78       please call DMXGetScreenCount(3X) first, and make sure attr  is  suffi‐
79       ciently large.
80
81       On  a  particular  back-end  server, it is possible that the associated
82       window has not yet been mapped because  the  XMapWindow(3X)  call  that
83       will  eventually  map  the  window  had  been buffered by Xlib's normal
84       buffering  system.   To  avoid  this  race   condition,   please   call
85       DMXSync(3X) before communicating directly with the back-end X server.
86

NAME

SYNOPSIS

DESCRIPTION

RETURN VALUE

NOTES

SEE ALSO