Update: UltraVNC 1.4.3.6 and UltraVNC SC 1.4.3.6: viewtopic.php?t=37885
Important: Please update to latest version before to create a reply, a topic or an issue: 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://twitter.com/ultravnc1
- Reddit community: https://www.reddit.com/r/ultravnc
- OpenHub: https://openhub.net/p/ultravnc

Patch to get the Option Key working on OSX connections

Post Reply
gjpc
8
8
Posts: 8
Joined: 2009-05-01 19:38

Patch to get the Option Key working on OSX connections

Post by gjpc »

While not being a registered developer, I have patched the current Source Forge tarball so I am cross posting my patch here.

I have a patch that enables uVNC to send the option key to OSX machines using the native OSX connection.

It is simple: in file keysymdefjap.h line 1506 change XK_Super_L from 0xFFEB to 0xFFE8

The tarball did not compile out of the box. I had to remove line 5 #include <d3dx9.h> from directxviewer.h
I had to add the ./omnithread directory to the vncviewer includes directories
I also manually moved the omnithread.lib into the vncviewer build directory, I am prefer Eclipse so I do not want to figure out the vagaries of VStudio.
Once I added nasm to my cygwin the viewer did build.

I do not use uVNC to connect to Win machines so I don't not know if this change is a burden for win to win users.
If they need the key, then a check box in the configuration would be appropriate to switch between the two values in the ClientConnection.cpp ID_VK_LWINDOWN & ID_VK_LWINUP message handlers around line 6723.

Due to the very low activity in the developer forum, especially about patching I am reluctant to go any further with my patch then what I have.

Enjoy
Post Reply