24 |
One line may not exceed 1024 bytes, including newline. |
One line may not exceed 1024 bytes, including newline. |
25 |
|
|
26 |
The protocol has no concept of hidden or unmapped windows. A window does not |
The protocol has no concept of hidden or unmapped windows. A window does not |
27 |
exist unless it is visible. Note that a minimised window is an exception to |
exist unless it is visible. Note that a minimized window is an exception to |
28 |
this rule. |
this rule. |
29 |
|
|
30 |
Data types |
Data types |
45 |
Allocate structures for a new window. |
Allocate structures for a new window. |
46 |
|
|
47 |
Syntax: |
Syntax: |
48 |
CREATE,<ID>,<FLAGS> |
CREATE,<ID>,<PARENT>,<FLAGS> |
49 |
|
|
50 |
|
Indicates that a window has appeared on the server. If PARENT is non-zero then |
51 |
|
the new window is a child of that window (it's transient for it). |
52 |
|
|
53 |
Note that very little information is included in this message. Things like |
Note that very little information is included in this message. Things like |
54 |
title and state will come in subsequent messages. This message should only |
title and state will come in subsequent messages. This message should only |
73 |
POSITION,<ID>,<X>,<Y>,<WIDTH>,<HEIGHT>,<FLAGS> |
POSITION,<ID>,<X>,<Y>,<WIDTH>,<HEIGHT>,<FLAGS> |
74 |
|
|
75 |
If the window isn't visible yet (because a |
If the window isn't visible yet (because a |
76 |
STATE hasn't been set or because it's minimised), you must store the position |
STATE hasn't been set or because it's minimized), you must store the position |
77 |
and size. A new POSITION is not guaranteed to be sent when the window changes |
and size. A new POSITION is not guaranteed to be sent when the window changes |
78 |
state. |
state. |
79 |
|
|
88 |
The text is guaranteed to be stripped of control characters (< 0x20). |
The text is guaranteed to be stripped of control characters (< 0x20). |
89 |
|
|
90 |
Note that this has the same requirement as POSITION, that the title needs to |
Note that this has the same requirement as POSITION, that the title needs to |
91 |
be stored for newly created windows until a STATE is sent. |
be stored for newly created windows until a STATE is sent. It is however not |
92 |
|
guaranteed that a TITLE will be sent before the first STATE. |
93 |
|
|
94 |
|
|
95 |
ZCHANGE |
ZCHANGE |
113 |
|
|
114 |
State can have one of three values: |
State can have one of three values: |
115 |
0 : "Normal" window. |
0 : "Normal" window. |
116 |
1 : Minimised. |
1 : Minimized. |
117 |
2 : Maximised. |
2 : Maximized. |
118 |
|
|
119 |
|
The initial STATE for a window will always be preceeded by one CREATE and one |
120 |
|
POSITION. Optionally, a TITLE may also be sent before the first STATE. |
121 |
|
|
122 |
DEBUG |
DEBUG |
123 |
----- |
----- |
163 |
Syntax: |
Syntax: |
164 |
SYNC,<FLAGS> |
SYNC,<FLAGS> |
165 |
|
|
166 |
For each window, the server will send CREATE, POSITION and SETSTATE just as |
For each window, the server will send CREATE, POSITION and STATE, in that |
167 |
if the window was created. |
order, just as if the window was created. Note that a TITLE may also, |
168 |
|
optionally, be sent before the STATE. |
169 |
|
|
170 |
POSITION |
POSITION |
171 |
-------- |
-------- |