Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: https://forum.uvnc.com/viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- 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
Important: Please update to latest version before to create a reply, a topic or an issue: https://forum.uvnc.com/viewtopic.php?t=37864
Join us on social networks and share our announcements:
- Website: https://uvnc.com/
- GitHub: https://github.com/ultravnc
- Mastodon: https://mastodon.social/@ultravnc
- 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
1.3.5 dev-1
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
1.3.5 dev-1
Title wil be something like "Connect from ip/ID" instead of "UltraVNC Connection...".
I want to keep the viewers ip address in it, fixed.
Content " UltraVNC is controlling your" can be send by the viewer. ( max 255 chars), dynamic
Where is the best spot to input the text on connect or with the password ?
Do we need to add some control ? Or only show it when the viewer added some message. ?
There was also a request for adding a color transparent border around the desktop while it's under vnc control ?
Feedback
Re: feedback for request "Notify the user on connection."
I do like the idea in general.
First regarding user control:
There should be no setting on client side to completely overrule the server configuration to show a notification as this is entirely a server-side decision. If the server operator wants to get notified about connections then usually you intend to force this notification. But perhaps server-side control could be done with some radio buttons...
This would give full control to server operators how the indicators would be displayed. When the sharing indicator frame is enabled a frame around the shared screen (much like many screensharing/collaboration tools are doing could be displayed around the edge of each shared display. Clients should not be able to overrule this setting at all when enabled.
For the desktop notification I would allow server operators to enable or disable them entirely. When enabled it could be a good idea to allow server operators to enforce showing it. If the client does not provide any text it might just show a generic message like "VNC Client connected" and information about source IP/hostname. If the client is providing custom text it might replace "VNC CLient connected" header but still show information about the client like source IP/hostname.
If the radio buton is set to "Show only if client provides notification information" UVNC server might omit the message if client does not provide any custom text. So the client could control if any notification is shown.
On client-side I would prefer if the "Connection notification identifier" text can be configured in advanced settings. Perhaps in "Misc" settings. I would personally enter my name into the field to let users know who actually connected.
First regarding user control:
There should be no setting on client side to completely overrule the server configuration to show a notification as this is entirely a server-side decision. If the server operator wants to get notified about connections then usually you intend to force this notification. But perhaps server-side control could be done with some radio buttons...
Code: Select all
Connection notifications:
[x] Sharing indicator frame around shared screen
[x] Show notification on connect
Notification control:
(x) Always show on client connect
( ) Show only if client provides notification information
For the desktop notification I would allow server operators to enable or disable them entirely. When enabled it could be a good idea to allow server operators to enforce showing it. If the client does not provide any text it might just show a generic message like "VNC Client connected" and information about source IP/hostname. If the client is providing custom text it might replace "VNC CLient connected" header but still show information about the client like source IP/hostname.
If the radio buton is set to "Show only if client provides notification information" UVNC server might omit the message if client does not provide any custom text. So the client could control if any notification is shown.
On client-side I would prefer if the "Connection notification identifier" text can be configured in advanced settings. Perhaps in "Misc" settings. I would personally enter my name into the field to let users know who actually connected.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: feedback for request "Notify the user on connection."
SkyBeam .. vote +1
..also cover the case that old viewers can't send it.Show only if client provides notification information
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: feedback for request "Notify the user on connection."
Good news, all is implemented.
Also the screen blanking is back working on windows 10
Current only tested as application, still need to run some service tests.
Downloads
https://www.uvnc.eu/download/1351/UltraVnc_1351.zip
https://www.uvnc.eu/download/1351/Ultra ... _Setup.exe
https://www.uvnc.eu/download/1351/Ultra ... _Setup.exe
Also the screen blanking is back working on windows 10
Current only tested as application, still need to run some service tests.
Downloads
https://www.uvnc.eu/download/1351/UltraVnc_1351.zip
https://www.uvnc.eu/download/1351/Ultra ... _Setup.exe
https://www.uvnc.eu/download/1351/Ultra ... _Setup.exe
Re: feedback for request "Notify the user on connection."
I did a test on the feature and it basically works as expected except for one detail where I am not sure if it was done on purpose or not:
When the radio button is on "Always show on client connect" the notification displayed is always a generic one. The custom message from the client is never taken into account. I was assuming that the "Always show on client connect" just enforcing a message to be displayed no matter if the client is providing one (if the client is not providing a message it just uses the fallback default message). And when using the "Show only if client provides notification information" will not show any notification if the client is not sending one.
Also I noticed that the notification is still shown even if the option is set to "Show only if client provides notification information" and the notification text is empty on client side when connecting.
So two things I would (personally) change:
I also noticed another thing: This new feature is somehow overlapping with the incoming connection query window. What about displaying the client connection message also in the incoming connection query window? So when a supporter connects and provides a message like "Hi, I am Dave from IT department" this would be displayed in the connection query window too. So the query window would display the message configured on server side like "Incoming VNC connection. Would you like to accept the connection?
Message from remote client: Hi, I am Dave from IT department"
So simply the message could be added to the connection query window if enabled.
Also the settings clusters in the property window could be grouped as they somehow belong to each other then. Allowing the user to enable the query window and notifications.
Regarding property window: I noticed that the ne3w notification settings do not show up in configuration panels (uvnc_settings) but only in server admin properties. Anyhow the split of those settings is and was always confusing to me (properties, admin properties, uvnc_settings). Perhaps this could need a cleanup.
When the radio button is on "Always show on client connect" the notification displayed is always a generic one. The custom message from the client is never taken into account. I was assuming that the "Always show on client connect" just enforcing a message to be displayed no matter if the client is providing one (if the client is not providing a message it just uses the fallback default message). And when using the "Show only if client provides notification information" will not show any notification if the client is not sending one.
Also I noticed that the notification is still shown even if the option is set to "Show only if client provides notification information" and the notification text is empty on client side when connecting.
So two things I would (personally) change:
- When set to "Always show on client connect" use the client message when provided but default message if nothing provided by client
- When set to "Show only if client provides notification information": Do not display notification if no message supplied by client (or message is zero length after trimming)
I also noticed another thing: This new feature is somehow overlapping with the incoming connection query window. What about displaying the client connection message also in the incoming connection query window? So when a supporter connects and provides a message like "Hi, I am Dave from IT department" this would be displayed in the connection query window too. So the query window would display the message configured on server side like "Incoming VNC connection. Would you like to accept the connection?
Message from remote client: Hi, I am Dave from IT department"
So simply the message could be added to the connection query window if enabled.
Also the settings clusters in the property window could be grouped as they somehow belong to each other then. Allowing the user to enable the query window and notifications.
Regarding property window: I noticed that the ne3w notification settings do not show up in configuration panels (uvnc_settings) but only in server admin properties. Anyhow the split of those settings is and was always confusing to me (properties, admin properties, uvnc_settings). Perhaps this could need a cleanup.
Re: feedback for request "Notify the user on connection."
Minor feedback, vncviewer.exe shows product version dev 1.3.5.1.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: feedback for request "Notify the user on connection."
version is correct dev 1.3.5.1, images where taken before final test build.
1.3.4 -> stable
1.3.5 -> development
1.3.6 -> stable ( 01/01/22)
1.3.4 -> stable
1.3.5 -> development
1.3.6 -> stable ( 01/01/22)
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: development 1.3.5.1
ok, the notification messages will be appended to Accept/Reject message
Accept/Reject message = server custom string (ini) + newline + viewer custom string ( network)
Current 1.3.5.1 removed, the protocol required a change for this and could not be handled with the 1.3.5.1 test protocol.
Accept/Reject message = server custom string (ini) + newline + viewer custom string ( network)
Current 1.3.5.1 removed, the protocol required a change for this and could not be handled with the 1.3.5.1 test protocol.
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact:
Re: development 1.3.5.1
Uploaded as 1.3.5.2.
Custom message is appended to the Accept/reject dialog
Downloads
https://www.uvnc.eu/download/1352/UltraVnc_1352.zip
https://www.uvnc.eu/download/1352/Ultra ... _Setup.exe
https://www.uvnc.eu/download/1352/Ultra ... _Setup.exe
Custom message is appended to the Accept/reject dialog
Downloads
https://www.uvnc.eu/download/1352/UltraVnc_1352.zip
https://www.uvnc.eu/download/1352/Ultra ... _Setup.exe
https://www.uvnc.eu/download/1352/Ultra ... _Setup.exe
Re: development 1.3.5.1
I did another test with version 1.3.5.2 and I am happy you seem to have taken my feedback pretty serious
I confirm all tests I did just worked fine:
I confirm all tests I did just worked fine:
- I like the combined user query message and notification group in admin properties panel
- Red notification frame working as expected
- Notification message working as expected
- Notification message is properly shown no matter the custom message passed when the corresponding radio button is selected
- Notification message only showing up if custom message is provided by client when the corresponding radio button is selected
- Rudi De Vos
- Admin & Developer
- Posts: 6863
- Joined: 2004-04-23 10:21
- Contact: