[Bug 246121] [bhyve][PATCH] Append Keyboard Layout specified option for using VNC.

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246121

Koine Yuusuke <koinec at yahoo.co.jp> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #214725|0                           |1
        is obsolete|                            |
 Attachment #215004|text/x-uuencode             |text/plain
          mime type|                            |

--- Comment #7 from Koine Yuusuke <koinec at yahoo.co.jp> ---
Created attachment 215004
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215004&action=edit
[bhyve][PATCH] Support QEMU Extended Key Event Message and Append keyboard
layout specified option.

Thank you for telling me and I'm sorry for my lack of research.

With you help, I found that the TigerVNC supports QEMU Extended Key Event
Message, so I immediately tried to create a patch.
As a result, when using TigerVNC, it is possible to support keys unique of each
language without depending the keyboard layout setting file or specifying bhyve
-k option.
However, I would like to preserve the keyboard layout configuration file and
the bhyve -k option feature to allow use by VNC clients that don't support QEMU
Extended Key Event Messages (such as tightVNC).

By the last time, the keyboard layout setting file should have been able to
input alphabets, numbers, symbols, and a part of functional key(e.g.
Enter/Space) in every languages keyboard, so I think that support has advanced
considerably, but what about?


A. How to apply the NEW patch --------------------------------------------
  Same as last time. (See above)

B. Usage -----------------------------------------------------------------
  * VNC clients with supported the QEMU Extended Key Event Mesage (TigerVNC)
      Just use it as before.
      The keyboard layout of each language is automatically supported.
      Even if the -k option is specified, it will be ignored.

  * VNC clients WITHOUT supported the message (tightVNC, ssvnc, etc)
      You need to specify the keyboard layout name by the -k option.
      The method of specify the -k option is same as last time.
      If not specified, the US keyboard layout is assumed to have been
specified.

I apologize for fixing the path many times, but I appreciate your cooperation.

-- 
You are receiving this mail because:
You are the assignee for the bug.