-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java Viewer: Per-host options + the ability to save connection info files #135
Comments
(ported from the Windows TurboVNC Viewer) Refer to #135
The view-only and zoom hotkeys have been implemented in the latest 3.0 evolving build. The clipboard transfer hotkey isn’t a good fit for the Java viewer, since it has independent settings for disabling inbound and outbound clipboard transfer. (The clipboard transfer hotkey was implemented primarily as an easy workaround for the flaky daemon-based clipboard transfer mechanism that has long since been replaced.) |
(when non-automatic desktop scaling is enabled) Note that, unfortunately, there is no straightforward way to use '+' as an accelerator in Swing, since that character is usually not located on the primary keyboard layer. Because the key codes in Swing are only valid for a U.S. keyboard layout, there is not enough information in the KeyEvent to determine, with any degree of reliability, whether Ctrl-Alt-Shift + or Ctrl-Alt-Shift - has been pressed. Thus, the new implementation of this feature uses the 8 and 9 keys for, respectively, zooming out and in instead of the - and + keys. This provides a similar feel to the old implementation when using U.S. keyboards, since the 8 and 9 keys are also adjacent to the 0 key. Refer to #135
This partially resolves feature regressions introduced when the Windows TurboVNC Viewer was retired. Partially implements #135
Is there a possibility of providing the UI selection to options file mapping. |
@relcodedev Yeah, it's a bit nonintuitive, because the format of .vnc connection info files comes from TightVNC 1.3.x, and I had to map TurboVNC features onto that format. I'm about to replace all of that mess with a new .turbovnc connection info file format that just uses the TurboVNC Viewer command-line parameters. In the meantime, you can achieve what you want with
For other mappings, refer to: turbovnc/java/com/turbovnc/rfb/Params.java Lines 146 to 305 in d5e760c
|
Per-host options were implemented in the TurboVNC 3.1 evolving code base back in August. Later today, I plan to push a commit that implements a new .turbovnc connection info file format that accepts the same parameters and values that the TurboVNC Viewer accepts. However, upon further reflection, the ability to save connection info files doesn't make a lot of sense with the TurboVNC Session Manager and the advanced authentication features that the TurboVNC Viewer supports. If a TurboVNC session was started using the session manager, then (unless |
Since the Windows TurboVNC Viewer will be retired in the next major release, this is a catch-all issue for any GUI features from the Windows TurboVNC Viewer that still need to be ported into the Java TurboVNC Viewer, including:
The text was updated successfully, but these errors were encountered: