Skip to content
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

Exclude selected keys #1577

Closed
BenMcLean opened this issue Jan 9, 2023 · 3 comments
Closed

Exclude selected keys #1577

BenMcLean opened this issue Jan 9, 2023 · 3 comments
Labels
enhancement New feature or request wontfix This will not be worked on

Comments

@BenMcLean
Copy link

BenMcLean commented Jan 9, 2023

Is your feature request related to a problem? Please describe.
I am visually impaired and depend on Windows Magnifier (and its Linux equivalents when using Linux desktops) to use computers much of the time. This involves lots of zooming in and out with with Windows+Plus and Windows+Minus key combinations, as well as Windows+Esc for quick zoom-out. (annoying that Linux magnifiers typically don't duplicate that behavior.)

When in a VNC session, I'd like those three specific key combinations to affect the client computer, but all other system key combinations to affect the target computer, (except F8 to get the TigerVNC menu of course) largely because VNC doesn't handle Windows Magnifier well.

Describe the solution you'd like
Some option in TigerVNC to assign any number of arbitrary custom key combinations to stay with the client computer while transmitting all others to the target computer.

@RobyB
Copy link

RobyB commented Jan 11, 2023

Having a list of key combinations that stay with the client computer would really be a nice feature also for MacOs, especially when you run full-screen. In this case all key combinations are passed to the target computer.
By default things should stay as they are, but it would be nice to have a list of key combinations that you can specify in the config file that stay with the client computer.

@CendioOssman
Copy link
Member

I sympathise with the use case, but I'm afraid I don't think it is likely that we'll add any exclusion system like that. The technical complexity, and the complexity for the user in configuring something like this (there's always heaps of corner cases), is very high.

What we are hoping to achieve, is a simpler way to toggle the grab on and off, so that you can reach the local system easier. Please see #2 for that.

@CendioOssman CendioOssman added the enhancement New feature or request label Jan 11, 2023
@BenMcLean
Copy link
Author

I agree that a simple quick hotkey to toggle from remote keyboard to local keyboard and back would probably address this alright. Thanks.

@samhed samhed added the wontfix This will not be worked on label Jan 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants