Update accesskit to 0.24.0 and accesskit_consumer to 0.34.0#19
Update accesskit to 0.24.0 and accesskit_consumer to 0.34.0#19SuchAFuriousDeath wants to merge 1 commit intorerun-io:mainfrom
Conversation
SuchAFuriousDeath
force-pushed
the
update-accesskit-0.24
branch
from
6365bf7 to
9fa7d3f
Compare
|
Closed via #18. Sorry for the delay! |
|
@lucasmerlin Could there be a new release? Without it, all of this is kinda pointless 😅 |
|
@SuchAFuriousDeath we usually release kittest together with egui, and patch it until the release. Assuming you need the release to finish the wgpu update pr, the way forward would be to complete the accesskit update in egui: emilk/egui#7850, patching egui to use the updated kittest from main. Once that is merged you can update the wgpu branch from main and CI should pass |
|
I see. There was a bit of a comical situation with windows crate duplication. That's why I needed the accesskit update in here, because it will eventually deduplicate the windows crate and make egui compile with wgpu 28. Thanks for the advice. I'll do the update directly in emilk/egui#7853. |
2 participants
Update accesskit to 0.24.0 (was 0.21.0) and accesskit_consumer to 0.34.0 (was 0.30.0).
The only breaking change in accesskit 0.24.0 vs 0.23.0 is a MSRV bump to 1.85, which kittest already requires. The 0.23.0 release added multiple tree support (
TreeId,target_tree/target_nodesplit inActionRequest), and 0.22.0 had various type changes (Color struct, font size/weight as f32, etc.).No source code changes are needed in kittest since it passes
TreeUpdatethrough without inspecting the changed fields.This supersedes #18 by going directly to 0.24.0.