I'd like to expand this feature request to resolve khonsulabs/cushy#81. The ModifiersState that we can receive in ModifiersChanged doesn't allow us to read the NumLock or CapsLock states. This doesn't overlap with issue 1010 as an event-based API is still useful even before we have an api to mirror getkey, and it wasn't resolved by #753, though I'm not sure why.

Each KeyboardEvent implementation tracks numlock and capslock. Here's where they're read in linux:

winit/src/platform_impl/linux/common/xkb_state.rs

Lines 649 to 651 in cc33212

    
           self.caps_lock = mod_name_is_active(ffi::XKB_MOD_NAME_CAPS); 
        
           self.logo = mod_name_is_active(ffi::XKB_MOD_NAME_LOGO); 
        
           self.num_lock = mod_name_is_active(ffi::XKB_MOD_NAME_NUM);

(and here in windows)
but those aren't forwarded to the public ModifiersState

winit/src/platform_impl/linux/common/xkb_state.rs

Line 657 in cc33212

let mut to_mods = crate::keyboard::ModifiersState::empty();

	self.caps_lock = mod_name_is_active(ffi::XKB_MOD_NAME_CAPS);
	self.logo = mod_name_is_active(ffi::XKB_MOD_NAME_LOGO);
	self.num_lock = mod_name_is_active(ffi::XKB_MOD_NAME_NUM);

get NumLock status #1426

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions