77b866096d
Redesign framebuffer update loop
...
Rendering may now only happen inside the rendering callback. The user is
also allowed to change out the entire buffer in the callback.
The callback is triggered by nvnc_damage_region(), nvnc_damage_whole()
and/or framebuffer update requests.
This fixes #26
2020-04-07 23:35:57 +00:00
8fc5c18b28
Don't show partial frames to new clients
2020-04-04 14:00:03 +00:00
f45f90ed9b
nvnc_fb: Add a mechanism for signaling that a frame is in use
2020-04-04 12:33:18 +00:00
61efca48f0
damage: Increment/decrement reference count before/after check
...
This is prudent. The user might throw away these buffers before the
damage check finishes.
2020-01-29 21:33:13 +00:00
19e4e42036
Implement VeNCrypt with x509 plain authentication
2020-01-25 15:35:14 +00:00
80b1f3cb4c
Re-format using clang-format
2019-10-20 22:13:51 +00:00
e9f200f4cc
Excise y-inversion code
2019-10-08 17:58:35 +00:00
4beaf88a35
Turn around frame update model
...
Keeping a framebuffer for clients to request from seems to be a better fit for
the VNC standard.
2019-10-07 20:29:12 +00:00
3196a7a46b
Make nvnc_fb opaque
2019-10-07 17:39:54 +00:00
7d4af0e741
Encode on worker threads
2019-09-15 21:53:10 +00:00
70b2448c6e
Create utility function for checking buffer damage
2019-09-15 21:53:10 +00:00
b0fb22bdd6
Rename inc -> include for sake of convention
2019-09-14 16:07:34 +00:00
Andri Yngvason