-
Notifications
You must be signed in to change notification settings - Fork 54
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
When should the window be created hidden? #255
Comments
Thanks for the report. Can you please specify which platform(s) this is happening on? |
I have only tested this in Windows 11, I can try in Linux if you want, but not MacOS as I don't have a Mac 😄 |
You need to create the window invisible, then create the adapter, then show the window. I'm sorry I didn't make that clear in the accesskit_winit docs. This is crucial on Windows, and possibly important on macOS as well. |
Ohh, I will try that, Linux works btw 😄 |
Maybe we should panic if |
Yeah, that works ! ✨ You can close this issue if you want now 😄 But, maybe it could be clarified in the docs/examples. |
accesskit_winit
eats initial redraw request
Coming back to this, when exactly is it necessary to create the window hidden so that AccessKit can initialize properly?
Once the above items are resolved, we should add a platform-specific note to |
Solved by #278 |
Hey!
While I was working on accessibility support for Freya I noticed a weird behavior. The initial redraw request event never happens. So after some digging, I found out it only occurs when creating the Winit adapter
I have only tested this on Windows 11.
When creating the Winit adapter:
When not creating it :
I made a little reproduction example, the important line is this one
This issue is easy to fix by simply listening to the Init event of the eventloop and forcing a redraw request:
But, is still not the expected behavior and I wonder if it could be causing other problems I am not aware of.
Anyway, nice job with accesskit 👏
The text was updated successfully, but these errors were encountered: