-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Upgrade to ndk-sys 0.6.0
and ndk 0.9.0
#155
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -507,6 +507,7 @@ impl<'a> InputIteratorInner<'a> { | |
ndk::event::InputEvent::KeyEvent(e) => { | ||
input::InputEvent::KeyEvent(input::KeyEvent::new(e)) | ||
} | ||
_ => todo!("NDK added a new type"), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. hmmm, we probably shouldn't panic here. It would be a backwards compatible change to extend the ndk enum, and if we don't know about some new event in I guess for now lets be lazy and just keep this and it would presumably make sense to handle new events here but without knowing what kind of event might be added it's not obvious that a panic is reasonable here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah fair enough, we're currently only mapping |
||
}; | ||
|
||
// `finish_event` needs to be called for each event otherwise | ||
|
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.
By the way, I wondered if maybe the repr type should have been fixed as
game-activity
is converting them as well. That matches what I did in the NDK to match the enum type to the function(s) that consume/generate it, not to the defaultu32
that happens to be assigned to untypedenum
s.At some point that'll be fixed upstream anyway as they're retroactively fixing things to be
enum foo : int32_t
now that the NDK is always compiled withclang
.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.
But if I read things like this in
android-activity
again:It feels like most if not all enums that are redefined are not to capture differences with
game-activity
, but merely because thendk
crate was lagging behind Android (what the comment literally says).Instead of tediously spending a lot of time doing the same "type rectification" here, I'd rather extend the
ndk
with all the missing variants (which we're now allowed to do non-breaking thanks to using the exact same#[non_exhaustive] enum
setup asandroid-activity
), compare withandroid-activity
to make sure we're not missing out, and finally reduce some NIH :)