From 710d0620a41d16553393f2181abf660556b5d257 Mon Sep 17 00:00:00 2001 From: Matthew Jakeman Date: Wed, 2 Dec 2020 22:14:27 +0000 Subject: [PATCH] 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. --- gdk/win32/gdkevents-win32.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gdk/win32/gdkevents-win32.c b/gdk/win32/gdkevents-win32.c index 8652f8c5f3..b7488fbc1e 100644 --- a/gdk/win32/gdkevents-win32.c +++ b/gdk/win32/gdkevents-win32.c @@ -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);