Clarify that a=f is needed for chunked transmission of animation frame data
This commit is contained in:
parent
092dc3d01f
commit
a73f09cf89
1 changed files with 7 additions and 6 deletions
|
|
@ -330,12 +330,13 @@ sequence of escape codes to the terminal emulator::
|
|||
<ESC>_Gm=0;<encoded pixel data last chunk><ESC>\
|
||||
|
||||
Note that only the first escape code needs to have the full set of control
|
||||
codes such as width, height, format etc. Subsequent chunks **must** have
|
||||
only the ``m`` key. The client **must** finish sending all chunks for a single image
|
||||
before sending any other graphics related escape codes. Note that the cursor
|
||||
position used to display the image **must** be the position when the final chunk is
|
||||
received. Finally, terminals must not display anything, until the entire sequence is
|
||||
received and validated.
|
||||
codes such as width, height, format, etc. Subsequent chunks **must** have only
|
||||
the ``m`` and optionally ``q`` keys. When sending animation frame data, subsequent
|
||||
chunks must also specify the ``a=f`` key. The client **must** finish sending
|
||||
all chunks for a single image before sending any other graphics related escape
|
||||
codes. Note that the cursor position used to display the image **must** be the
|
||||
position when the final chunk is received. Finally, terminals must not display
|
||||
anything, until the entire sequence is received and validated.
|
||||
|
||||
|
||||
Querying support and available transmission mediums
|
||||
|
|
|
|||
Loading…
Reference in a new issue