Changes between Initial Version and Version 1 of Ticket #1432
- Timestamp:
- 02/07/17 10:26:15 (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #1432
-
Property
Status
changed from
new
toassigned
-
Property
Status
changed from
-
Ticket #1432 – Description
initial v1 1 1 Split from #1426. Maybe scrolling should be disabled in v1.x html5 clients, otherwise they will show display corruption when connecting to v2.x servers that provide the "scroll" encoding. (v1.x servers require video - which is not enabled by default) 2 2 3 Maybe the "flush" screen update attribute can be used as some kind of barrier: we can decode and paint the updates in parallel as they come in, but we should not start decoding a new group of screen updates until the current group has made it to the canvas. (this is only per-window, and there are no constraints on the paint ordering of screen updates within the same flush group)3 The "flush" screen update attribute can be used as some kind of barrier: we can decode and paint the updates in parallel as they come in, but we should not start decoding a new group of screen updates until the current group has made it to the canvas. (this is only per-window, and there are no constraints on the paint ordering of screen updates within the same flush group) 4 4 5 5 Ideally, we could start decoding the new screen updates, but just avoid updating the canvas. But that's likely to be much more difficult to implement.