update bevy to 0.14 and iced to a temp fork #32
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
hi,
related to #31
I was impatiently waiting for iced-rs/iced#2417 to update to bevy 0.14, which has been closed to move forward to a newer wgpu version, so not sure if we'll have a compatible iced release for this bevy version :(
I tried to use iced-rs/iced@ee7068c but I ran into some issue with wgpu buffer causing crash on second draw, because the buffer was still being mapped. To workaround this, I instead backported wgpu update on top of iced 0.12.1, which seems to work well.
Note that there are still some deprecation warnings from bevy_window related to keyboard input changes, but the examples work