You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Updating to bevy 0.12 / leafwing-input-manager 0.11.2
What you expected to happen
Handle<InputMap<A>> generates no errors, as it was valid before to use InputMap as an asset.
What actually happened
My code that used InputMap<A> as an asset (e.g. Handle<InputMap<A>>) is not working anymore.
Additional information
Apparently assets now should derive Asset instead of TypeUuid, and although it is a simple change, it unravels an issue I tried to fix in #386, because Asset requires TypePath, which can be provided by Reflect. And even though version 0.11 mentions that InputMap should be Reflect now, as far as I can tell it's not ?
The text was updated successfully, but these errors were encountered:
What would be the best course of action here ? I might reopen and port to multimap #386, if that is a good solution ? I would be glad to work on this and resolve it asap but I'm not sure what to actually do
Version
0.11.2
Operating system & version
NixOS (master)
What you did
Updating to bevy 0.12 / leafwing-input-manager 0.11.2
What you expected to happen
Handle<InputMap<A>>
generates no errors, as it was valid before to useInputMap
as an asset.What actually happened
My code that used
InputMap<A>
as an asset (e.g.Handle<InputMap<A>>
) is not working anymore.Additional information
Apparently assets now should derive
Asset
instead ofTypeUuid
, and although it is a simple change, it unravels an issue I tried to fix in #386, becauseAsset
requiresTypePath
, which can be provided byReflect
. And even though version 0.11 mentions thatInputMap
should beReflect
now, as far as I can tell it's not ?The text was updated successfully, but these errors were encountered: