-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Exposing the existing AndroidApp in the public API #3818
Copy link
Copy link
Closed
Labels
DS - androidAffects the Android backendAffects the Android backend
Milestone
Description
For my work on accesskit_winit, it would be helpful if winit exposed the existing AndroidApp instance in the public API, e.g. through an android_app method on ActiveEventLoopExtAndroid.
It's true that the top-level application already has the AndroidApp instance, since it has to pass that to winit in the first place. But that's not enough for accesskit_winit, for two reasons:
- Directly passing the
AndroidAppinstance from the application to accesskit_winit would require accesskit_winit to have a platform-specific adapter constructor for Android, and I'm trying to avoid platform-specific things in the accesskit_winit API, since the point of winit is to be cross-platform. - Having the application directly pass the
AndroidAppinstance to accesskit_winit would also break the layering that tends to happen in non-trivial applications. Consider thataccesskit_winit::Adapteris typically instantiated by a cross-platform framework like eframe or masonry.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
DS - androidAffects the Android backendAffects the Android backend