backends: Handle numlock saving/restoring directly in backends
Simplify the handling of numlock state, so it can be entirely handled within the input thread. Since the saving/restoring is triggered inside each backend code, there's no need anymore for meta_backend_set_numlock(). Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1403>
This commit is contained in:

committed by
Marge Bot

parent
23f95348fd
commit
f7fbd6ea6f
@@ -209,9 +209,6 @@ void meta_seat_impl_set_keyboard_map (MetaSeatImpl *seat_im
|
||||
void meta_seat_impl_set_keyboard_layout_index (MetaSeatImpl *seat_impl,
|
||||
xkb_layout_index_t idx);
|
||||
|
||||
void meta_seat_impl_set_keyboard_numlock (MetaSeatImpl *seat_impl,
|
||||
gboolean numlock_state);
|
||||
|
||||
void meta_seat_impl_set_keyboard_repeat (MetaSeatImpl *seat_impl,
|
||||
gboolean repeat,
|
||||
uint32_t delay,
|
||||
|
Reference in New Issue
Block a user