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
With network jitter, keys tend to be repeated on the server side due to intermittently delayed events. The best solution for this problem is to leave key repeat to the client and turn it off on the server.
We need to be able to communicate to the compositor that keys should not be repeated. The virtual keyboard protocol does not specify anything about repeated keys, so this will require some changes to the protocol, or perhaps even a new one.
However, wl_keyboard doesn't have a repeat event. This needs to be added so that some applications such as games don't break. In the meantime, we can send an up & down event sequence for repeat.
With network jitter, keys tend to be repeated on the server side due to intermittently delayed events. The best solution for this problem is to leave key repeat to the client and turn it off on the server.
We need to be able to communicate to the compositor that keys should not be repeated. The virtual keyboard protocol does not specify anything about repeated keys, so this will require some changes to the protocol, or perhaps even a new one.
The compositor also needs to communicate this to its clients using https://wayland.app/protocols/wayland#wl_keyboard:event:repeat_info
However,
wl_keyboard
doesn't have a repeat event. This needs to be added so that some applications such as games don't break. In the meantime, we can send an up & down event sequence for repeat.See: raspberrypi/bookworm-feedback#213
The text was updated successfully, but these errors were encountered: