You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When accessing Android mobile devices on which runs droidVNC-NG using libvncserver, we have to switch the vncviewer to the old outdated tight-VNC 1.3 on Windows. That is annoying.
As far as I see it, there is support for TightVNC-1.3 file transfer.
Is there any reason why the TightVNC-2.x file transfer is not implemented yet - besides the lack of resources?
Tight-VNC did not change there license it is still GPL2, so this could not be a reason.
Did somebody tried it already and did have some technical problems?
May be because it is difficult to integrate it in the current structure of libvncserver.
Thanks for any information on this topic.
The text was updated successfully, but these errors were encountered:
As far as I see it, there is support for TightVNC-1.3 file transfer.
Correct.
Is there any reason why the TightVNC-2.x file transfer is not implemented yet - besides the lack of resources?
Basically "just" lack of resources.
Tight-VNC did not change there license it is still GPL2, so this could not be a reason. Did somebody tried it already and did have some technical problems?
Not that I know.
May be because it is difficult to integrate it in the current structure of libvncserver.
While there's still lots of legacy cruft, we have updated the internal structure bit by bit, so that should not pose a problem.
If you'd like to put out an incentive for implementing this feature, you can do so at https://issuehunt.io/r/LibVNC/libvncserver
When accessing Android mobile devices on which runs droidVNC-NG using libvncserver, we have to switch the vncviewer to the old outdated tight-VNC 1.3 on Windows. That is annoying.
As far as I see it, there is support for TightVNC-1.3 file transfer.
Is there any reason why the TightVNC-2.x file transfer is not implemented yet - besides the lack of resources?
Tight-VNC did not change there license it is still GPL2, so this could not be a reason.
Did somebody tried it already and did have some technical problems?
May be because it is difficult to integrate it in the current structure of libvncserver.
Thanks for any information on this topic.
The text was updated successfully, but these errors were encountered: