You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The change made last year to import the Wayland key binding code into DRM https://github.com/Igalia/cog/commit/7b7c10b781a9cf2b64c1491a6766d68c45808fd8 seems to have semi-broken the key-repeat handling which now only fires once. Changing the repeat-key handler back from g_timeout_source_new() to g_source_new() restores proper operation.
Tried adding explicit g_source_set_ready_time() to the g_timeout_source_new() version, but it made no difference (even canceling and the setting a new timeout). The g_source_new() version included g_source_set_can_recurse=TRUE, but adding that to the g_timeout_source_new() version made no difference. The weirdest part is that after the single repeat, if you release the key and then press again, you get another single repeat.
Have GLib 2.74.6 installed. Nothing but reverting to the g_source_new() version seems to work for me.
The text was updated successfully, but these errors were encountered:
The change made last year to import the Wayland key binding code into DRM https://github.com/Igalia/cog/commit/7b7c10b781a9cf2b64c1491a6766d68c45808fd8 seems to have semi-broken the key-repeat handling which now only fires once. Changing the repeat-key handler back from g_timeout_source_new() to g_source_new() restores proper operation.
Tried adding explicit g_source_set_ready_time() to the g_timeout_source_new() version, but it made no difference (even canceling and the setting a new timeout). The g_source_new() version included g_source_set_can_recurse=TRUE, but adding that to the g_timeout_source_new() version made no difference. The weirdest part is that after the single repeat, if you release the key and then press again, you get another single repeat.
Have GLib 2.74.6 installed. Nothing but reverting to the g_source_new() version seems to work for me.
The text was updated successfully, but these errors were encountered: