Hi DRC,
Am 08.07.19 um 22:39 schrieb DRC:
On 7/7/19 5:31 AM, Torsten Kupke wrote:
I just tested the Java client again, because I remembered, that it
supports F8 to display a pulldown menu, which has a Close connection
entry. That's the way I use directly on the console of the TVNC server
to close the session connection. And yes, F8 works under Windows 10 1903
too. However I will use the native Windows client furthermore, because
of the missing bump scroll feature in the Java client. Therefore I would
prefer, that the native Windows client would support the F8 menu too.
The Windows 10 update number is confusing me. The latest update
(6/2019) was just made available to me, and I updated to it, but my
installation is still numbered 1803, not 1903. So I'm not 100% sure
that I am using the same version you are using. I can confirm, however,
that I am still unable to reproduce the hotkey problem despite updating
to the latest bits that are available as of today.
Your Windows 10 version definitly is one year older than my one. And
between both there was version 1809, which you missed too. Maybe you
only will get the newest version, if you explicitly search for Windows
Updates (there is a button in the Windows Update section of the Windows
Settings tool to do that). But be careful! Make a complete system
backup, before you start the version upgrade! If you don't upgrade,
Microsoft soon will stop support for your old version. Maybe Microsoft
will try to force you to upgrade. But maybe too, that your machine isn't
compatible with versions higher than 1803. In that case you should buy a
new one. ;-)
The equivalent of the F8 menu in the native Windows TurboVNC Viewer is
the Windows system menu, which is accessed by clicking on the upper left
of the title bar. Normally you could also pop up that menu with
Alt-Space, but the Windows TurboVNC Viewer transmits that key sequence
to the server. It is possible to implement an F8 menu in the native
Windows TurboVNC Viewer (which would basically just involve popping up
the existing system menu when F8 is pressed), but given that the native
Windows TurboVNC Viewer is going away in TurboVNC 3.0, I would much
rather spend my time shoring up any deficiencies that currently exist in
the Java TurboVNC Viewer vs. the native viewer.
Given that I am unable to reproduce the problem, there's no way I can
fix it. However, here are some possible solutions that I could
implement if your organization can provide funding for my labor:
1. An F8 menu in the native Windows TurboVNC Viewer. Given that this
would have to be implemented in the stable 2.2.x branch, I would need to
make it optional and disabled by default.
2. Allow Alt-Space to optionally pop up the native viewer's system menu
rather than transmitting that sequence to the server. This would also
have to be disabled by default. Given your general problems with any
Alt key sequences, you would need to first confirm that Alt-Space works
properly with other applications.
3. Add an option to the Java TurboVNC Viewer in TurboVNC 3.0 that would
allow the user to change the modifier key sequence used for the various
hotkeys. However, I'm not confident that this would fix the problem
you're experiencing, because if Alt-Enter isn't working, then that
points to a broader problem with modifier key events. Changing the
modifier keys probably wouldn't work around that problem.
My employer hardly will sponsor your work, because here too few users
use TuboVNC. And I myself only could pay via SEPA bank transfer. But I
don't know, wether this is possible to your country.
I surely will have to wait for TurboVNC 3.0, I think.
Best regards
Torsten
--
You received this message because you are subscribed to the Google Groups "TurboVNC
User Discussion/Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/turbovnc-users/3e97e85a-cd53-268a-5578-8b9671b15dd0%40hacon.de.
For more options, visit https://groups.google.com/d/optout.
