Continuous updates extension from TurboVNC #557
+2,142
−11
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
VelorumS
force-pushed
the
feat/continuous-updates
branch
2 times, most recently
from
0c3aa75 to
687d7a1
Compare
VelorumS
force-pushed
the
feat/continuous-updates
branch
10 times, most recently
from
1e83bdc to
875afd0
Compare
VelorumS
force-pushed
the
feat/continuous-updates
branch
from
875afd0 to
8941e02
Compare
|
Any progress on it? |
|
Hi @Neustradamus and @VelorumS similar closed issue on rustvncserver: rustvnc/rustvncserver#19 |
Author
|
@dustinmcafee there were no reviewers. If there are people with the permission to approve who are interested, I can try to rebase this PR. |
Member
|
@VelorumS you don't have to take the effort right now. I'll let you know once I have more time. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basically continuous updates extension as it is in the TurboVNC.
Built on Linux, tried with noVNC.
Probably doesn't fit the LibVNC code modularity requirements, but adds another case.
Taken at this point: TurboVNC/turbovnc@ff35d99