Skip to content
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

Possible solution to keep created surface consistent #3695

Open
ztlwk opened this issue May 11, 2024 · 0 comments
Open

Possible solution to keep created surface consistent #3695

ztlwk opened this issue May 11, 2024 · 0 comments
Labels
DS - android S - enhancement Wouldn't this be the coolest?

Comments

@ztlwk
Copy link

ztlwk commented May 11, 2024

Description

Proposed Change

  • Require the user to implement a "bridge" type, which owns the corresponding surface, and gets dropped and recreated by winit when being suspended in Android.
  • Make the "bridge" type or ApplicationHandler trait include the window recreation logic, so winit can recreate the window and own it, which assured the users to have a "window" in every update.

Relevant platforms

Android

@ztlwk ztlwk added the S - enhancement Wouldn't this be the coolest? label May 11, 2024
@ztlwk ztlwk changed the title Possible solution to keep raw window handle vaild to user Possible solution to keep created surface valid to user May 11, 2024
@ztlwk ztlwk changed the title Possible solution to keep created surface valid to user Possible solution to make surface creation safe May 30, 2024
@ztlwk ztlwk changed the title Possible solution to make surface creation safe Possible solution to keep created surface consistent May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DS - android S - enhancement Wouldn't this be the coolest?
Development

No branches or pull requests

2 participants