After more 1 000 000 (one million) views on forum for 1.5.0.x development versions... and 1.6.0.0 version
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
A new stable version, UltraVNC 1.6.1.0 and UltraVNC SC 1.6.1.0 have been released: https://forum.uvnc.com/viewtopic.php?t=38080
Feedback is welcome
Celebrating the 22th anniversary of the UltraVNC (25th anniversary since the laying of the foundation stone): https://forum.uvnc.com/viewtopic.php?t=38031
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Forum password change request: https://forum.uvnc.com/viewtopic.php?t=38078
Development: UltraVNC development is always here... Any help is welcome.
A new development version, UltraVNC 1.6.3.0-dev has been released, please test it: https://forum.uvnc.com/viewtopic.php?t=38091
Feedback is welcome
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- Bluesky/AT Protocol: https://bsky.app/profile/ultravnc.bsky.social
- Facebook: https://www.facebook.com/ultravnc1
- X/Twitter: https://x.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc
file transfer: remember local and remote paths
file transfer: remember local and remote paths
Really simple, but annoying thing is that I have to navigate to the right folders every time I open the file transfer windows. it will always default to the root. Could you remember the local and remote paths at least in the same session? Thanks a lot.
Re: file transfer: remember local and remote paths
I vote, yes 

UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: file transfer: remember local and remote paths
Thanks! Can you include this in the next RC? 

Re: file transfer: remember local and remote paths
only experienced user, not developer at all
UltraVNC 1.0.9.6.1 (built 20110518)
OS Win: xp home + vista business + 7 home
only experienced user, not developer
OS Win: xp home + vista business + 7 home
only experienced user, not developer
Re: file transfer: remember local and remote paths--plus...
My additional recommendations for file transfer enhancements, in my order of preference:
1 - make it so the filelists can be sorted by clicking on the column headers. e.g. clicking on "modified" sorts the list by date.
2 - make the remote & local path fields editable. If there's a typo in the entered path then either throw back an error, or go as far down the entered path as possible (i.e. change directory) before indicating the error.
2a - Above-&-Beyond Feature, for the local machine, anyway: incorporate the autocomplete feature found in many file-open interfaces when editing the path field on the local machine.
3 - Either "gray out" the main VNC window when the FT window is open, or -- I don't know if this is possible -- make windowing such that the FT window is always in front of -- never behind -- the main window.
3a - Actually, this would be good for the client list window too. That little bugger dives to the bottom window layer, and if you forget about him, you wonder why the "List All Clients" menu command stopped working. (Maybe for this guy, at least bring him to the front if he's already open when you do the "List All Clients" menu command )
Thanks for considering!
1 - make it so the filelists can be sorted by clicking on the column headers. e.g. clicking on "modified" sorts the list by date.
2 - make the remote & local path fields editable. If there's a typo in the entered path then either throw back an error, or go as far down the entered path as possible (i.e. change directory) before indicating the error.
2a - Above-&-Beyond Feature, for the local machine, anyway: incorporate the autocomplete feature found in many file-open interfaces when editing the path field on the local machine.
3 - Either "gray out" the main VNC window when the FT window is open, or -- I don't know if this is possible -- make windowing such that the FT window is always in front of -- never behind -- the main window.
3a - Actually, this would be good for the client list window too. That little bugger dives to the bottom window layer, and if you forget about him, you wonder why the "List All Clients" menu command stopped working. (Maybe for this guy, at least bring him to the front if he's already open when you do the "List All Clients" menu command )
Thanks for considering!
Max