wxKeyCode: add WXK_LAUNCH_[0-9A-F] for gtk bindings
X11 defines Xf86Launch[0-9a-f], which are then also defined as GDK_KEY_Launch[0-9A-F]. Unfortunately, keys which are not mapped are just plain ignored and the application is then not able to receive these keyboard events at all. The original PR https://github.com/wxWidgets/wxWidgets/pull/157 mapped only LaunchA/B to WXK_LAUNCH_APP1/2, this patch adds the whole range of keys and keeps LAUNCH_A/B as aliases for WXK_LAUNCH_APP1/2
This commit is contained in:
@@ -493,6 +493,21 @@ const char* GetVirtualKeyCodeName(int keycode)
|
||||
WXK_(LAUNCH_MAIL)
|
||||
WXK_(LAUNCH_APP1)
|
||||
WXK_(LAUNCH_APP2)
|
||||
WXK_(LAUNCH_0)
|
||||
WXK_(LAUNCH_1)
|
||||
WXK_(LAUNCH_2)
|
||||
WXK_(LAUNCH_3)
|
||||
WXK_(LAUNCH_4)
|
||||
WXK_(LAUNCH_5)
|
||||
WXK_(LAUNCH_6)
|
||||
WXK_(LAUNCH_7)
|
||||
WXK_(LAUNCH_8)
|
||||
WXK_(LAUNCH_9)
|
||||
// skip A/B which are duplicate cases of APP1/2
|
||||
WXK_(LAUNCH_C)
|
||||
WXK_(LAUNCH_D)
|
||||
WXK_(LAUNCH_E)
|
||||
WXK_(LAUNCH_F)
|
||||
#undef WXK_
|
||||
|
||||
default:
|
||||
|
Reference in New Issue
Block a user