A PR to match the Bevy 0.14.0-rc.2 release. Most of the change seem straightforward, although I'm not as familiar with the internals here as I'd like. The vast majority of the PR is app.world refactors to use function access.
Most notably:
bevy_egui has a pr open for 0.14, so I'm using that as a dependency in this PR which will have to be switched out.
Both Reflect::try_apply implementations for CustomAxisProcessor and CustomDualAxisProcessor are todo! because I'm not sure how to fill it out yet.
Additionally, there seems to be an issue on main with the mouse_position example, and that issue is still present here in this PR.
❯ cargo run --example mouse_position
warning: `leafwing-input-manager` (lib) generated 2 warnings
Compiling leafwing-input-manager v0.14.0 (/Users/chris/github/leafwing-studios/leafwing_input_manager)
error[E0432]: unresolved import `leafwing_input_manager::systems::run_if_enabled`
--> examples/mouse_position.rs:3:69
|
3 | axislike::DualAxisData, plugin::InputManagerSystem, prelude::*, systems::run_if_enabled,
| ^^^^^^^^^^^^^^^^^^^^^^^ no `run_if_enabled` in `systems`
error[E0599]: no variant or associated item named `ReleaseOnDisable` found for enum `InputManagerSystem` in the current scope
--> examples/mouse_position.rs:16:45
|
16 | .before(InputManagerSystem::ReleaseOnDisable)
| ^^^^^^^^^^^^^^^^ variant or associated item not found in `InputManagerSystem`
Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `leafwing-input-manager` (example "mouse_position") due to 2 previous errors
A PR to match the Bevy 0.14.0-rc.2 release. Most of the change seem straightforward, although I'm not as familiar with the internals here as I'd like. The vast majority of the PR is app.world refactors to use function access.
Most notably:
Reflect::try_apply
implementations forCustomAxisProcessor
andCustomDualAxisProcessor
aretodo!
because I'm not sure how to fill it out yet.Additionally, there seems to be an issue on main with the
mouse_position
example, and that issue is still present here in this PR.