Gdk4/Win32: Correct call to gdk_key_event_new()

The keycode and modifier (state) parameters are in the wrong order
for gdk_key_event_new() in the gdk win32 backend, which causes
key up/down events to be populated incorrectly.
This commit is contained in:
Matthew Jakeman 2020-12-02 22:14:27 +00:00 committed by Matthias Clasen
parent 770e848953
commit 710d0620a4

View File

@ -2096,8 +2096,8 @@ gdk_event_translate (MSG *msg,
window,
device_manager_win32->core_keyboard,
_gdk_win32_get_next_tick (msg->time),
state,
keycode,
state,
is_modifier,
&translated,
&translated);
@ -2170,8 +2170,8 @@ gdk_event_translate (MSG *msg,
window,
device_manager_win32->core_keyboard,
_gdk_win32_get_next_tick (msg->time),
build_key_event_state (key_state),
0,
build_key_event_state (key_state),
FALSE,
&translated,
&translated);
@ -2183,8 +2183,8 @@ gdk_event_translate (MSG *msg,
window,
device_manager_win32->core_keyboard,
_gdk_win32_get_next_tick (msg->time),
build_key_event_state (key_state),
0,
build_key_event_state (key_state),
FALSE,
&translated,
&translated);