AccessKit / AccessKit/accesskit
Request: Winit 0.31 support
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 114
- Avg merge
- 8h 25m
- Merged PRs (30d)
- 28
Description
Winit 0.31 beta has been released, and AccessKit (specifically accesskit-winit will need to be updated to support it).
Some notes:
- Winit 0.31 removes the generic
UserEventtype from theEventLoopProxy. It's replacement is a simplewake_upfunction. The idea is that you would send your actual message through something like a channel (std::mpsc, or similar). - Winit now has a type-and-trait only
winit-corecrate.
I suspect that:
- AccessKit should be able to depend on just
winit-core(it should not need to depend onwinit) - Rather than trying to directly send events to the Winit
EventLoopProxy, it should probably just accept a callback and let the user choose what they do with the events.
(I may have some time to work on this)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the accesskit-winit integration and comparing its EventLoopProxy usage with Winit 0.31's wake_up API and winit-core crate. Determine whether the integration can depend on winit-core and how event delivery should use a callback or channel. Done means accesskit-winit supports Winit 0.31 without the removed generic UserEvent type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- accessibility, desktop-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100