-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Use large parts of keyboard-types
#4026
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Looking forward to seeing this merged! Currently Blitz is using some custom code to convert between Winit events and keyboard_type events. I expect to do the same thing in Masonry. |
53dce06 to
d2c4d1b
Compare
848ffc1 to
02d3456
Compare
kchibisov
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the concern with certain keys being deprecated is resolved? e.g. Copy key.
If it's true, then it's probably fine.
Yup, I didn't deprecate those in rust-windowing/keyboard-types#49. |
02d3456 to
7651fe8
Compare
|
I've released v0.8.0 of |
7651fe8 to
5011462
Compare
5011462 to
410fc7a
Compare
410fc7a to
c7b2eb9
Compare
|
\o/ |
Use and re-export
keyboard_types::NamedKey,keyboard_types::Codeandkeyboard_types::Locationfrom thekeyboard-typescrate.Unsure what the best way to re-export these is, we might for example want
#[doc(inline)]?I haven't used
keyboard_types::Modifiersyet, since that has a differentserdeimplementation, which is kind of an ABI break and might be hard for downstream to handle, see #4018 (comment). Also, it's not really compatible for other reasons, see #2394 (comment).Part of #2394. See also rust-windowing/keyboard-types#60.