I would never do an official release for one bug fix unless it was
really critical. However, the 3.1.1 release is overdue, and there are
already enough bug fixes to justify it. Thus, I am trying to resolve
all outstanding issues in preparation for it.
Thank you for testing.
On 1/18/24 2:57
Ok, ok, I didn't want to force you to provide a new official release
with this fix. It was only, because I normally reluctantly use any
prerelease versions for working. But now I did it to be able to give you
feedback.
Short answer: Yes, the issue is fixed in this version!
Long answer: Before
Of course I would not push a commit to a Stable Active branch of our
GitHub repository unless I intended to eventually release it. (Please
refer to this article https://turbovnc.org/DeveloperInfo/Versioning for
more information on how our git branches correspond to TurboVNC release
series.)
H
Great! Will this fix be in the next official release of TurboVNC? Then I
would wait for it.
I didn't notice yet, that my Windows grabs F10. I really thought, that
the issue happens inside the TVNC session.
Many thanks again for your valuable work!
Am 17.01.2024 um 18:07 schrieb 'DRC' via Tur
Should be fixed in the latest pre-release builds:
https://turbovnc.org/DeveloperInfo/PreReleases
This was a similar issue to
https://github.com/TurboVNC/turbovnc/issues/349
Apparently Windows 10 started hijacking F10 for the same purpose as left
Alt at some point. Note that Windows 10 has do
It's really hard to track all of the relevant information across
multiple simultaneous bug reports from multiple people on a mailing
list. In the future, if you have multiple issues to report, it would be
better to file GitHub issues for each. In particular, the other thread
regarding bump sc
Hi DRC,
but how could a wrong key mapping be responsible for the fact, that only
each second pressing of F10 is passed to the debugger, and that I have
to click into the window to make F5 or Shift+F11 working (although the
cursor is blinking there already), when I had pressed F10 before? That
TurboVNC 3.1 introduced server-side key mapping, whereby the viewer
sends raw scan codes to the server and the server translates those into
X11 keysyms based on the key map that is active in the TurboVNC
session. Thus, the key map in the TurboVNC session now matters, and the
key map on the cli
Hi,
I'm a software developer using Qt Creator under Ubuntu. Since the recent
upgrade to Ubuntu 22.04 and installing TVNC 3.1 I have the problem,
that, when debugging my code with gdb in Qt Creator, that some keys
don't work as usual. For some details see
https://forum.qt.io/topic/153654/some-
