Updated bracket-bevy to Bevy 0.11.0

[IAmSegfault]

As mentioned in this issue, I updated bracket-bevy to use Bevy 0.10.1.

I Replaced stages with stageless sets. I also Replaced the function body of update_mouse_position to handle Window entities, with a workaround for the panic I mentioned. I also edited the Msaa resource so it reflects that it's an enum. I'm not sure how this branch is being used so if you would prefer the merge go into master as not to deal with merge conflicts let me know.

EDIT:

I added some changes to this pull request so that bracket-bevy now depends on Bevy 0.11.0. Changes were made to use the new scheduling system in 0.11.0. More testing is likely going to be needed however before merging this pull request.

I did notice two different bugs that occur rarely that both seem to happen once per 70-100 application launches. The first one appears to happen no matter what and results in a window with a gray screen and none of the systems appear to run. I'm not exactly sure what causes it because I can only reproduce the issue when running the application from a terminal, running from Visual Studio Code cannot seem to trigger the issue.

The second appears to happen if there are two or more different systems in the application that call the set() method on BracketContext. Changing the schedules of the systems and forcing them to execute in a specific order using .after() on the systems did not seem to resolve the issue. In this case it will occasionally cause this line in Bevy's render function to panic.

[sparr]

Is this intended to support GUI pseudo-terminals only? I'm trying to port my existing project using bevy + bracketlib over to using your updated bracket-bevy but disabling default features on bracketlib and enabling curses still leads to bevy creating a GUI terminal

[IAmSegfault]

Yes, bracket-bevy utilizes Bevy's renderer to provide a gui based pseudo terminal. I'm not sure if the curses backend is currently in a working state.

[sparr]

Thanks for the update. I'll keep using my own much less capable hacked-together bracket+bevy stack (https://github.com/sparr/ascii-factory/blob/main/src/bevy_bracket.rs) for now. I'd love to contribute here, but my Rust isn't sharp enough yet to dive into a codebase as complex as yours.

[thebracket]

After a really long absence, I'm trying to schedule some bracket lib in the next month. Toddler, burnout, Covid and a mother with extreme health issues got me.

My plan is to bring it up to the latest Bevy, and make some better examples. Recent Bevy changes will mean redoing some parts. (The Bevy changes also delayed the next book I'm working on, which uses Bevy.)

On Sat, Dec 30, 2023, 10:57 AM sparr @.***> wrote:

Thanks for the update. I'll keep using my own much less capable hacked-together bracket+bevy stack for now. I'd love to contribute here, but my Rust isn't sharp enough yet to dive into a codebase as complex as yours.

— Reply to this email directly, view it on GitHub https://github.com/amethyst/bracket-lib/pull/342#issuecomment-1872564788, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADRU4344HE7I5SZHM3KMUX3YMBBYTAVCNFSM6AAAAAAYY2YEVKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZSGU3DINZYHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>