bevy/crates/bevy_app at b39f83640fce7ae385cc4f02c439e28f562ecdc8 - Mirrors/bevy

mirror of https://github.com/bevyengine/bevy synced 2024-11-14 00:47:32 +00:00

History

Edgar Geier d3e426e86f Use default schedule consistently in `add_state` (#7751 ) # Objective When working on #7750 I noticed that `CoreSchedule::Main` was explicitly used to get the schedule for the `OnUpdate` set. This can lead to failures or weird behavior if `add_state` is used with a differently configured `default_schedule_label`, because the other systems are added to the default schedule. This PR fixes that. ## Solution Use `default_schedule_label` to retrieve a single schedule to which all systems are added.	2023-02-20 22:06:34 +00:00
..
src	Use default schedule consistently in `add_state` (#7751 )	2023-02-20 22:06:34 +00:00
Cargo.toml	Release 0.9.0 (#6568 )	2022-11-12 20:01:29 +00:00

Edgar Geier d3e426e86f Use default schedule consistently in add_state (#7751 )

# Objective

When working on #7750 I noticed that `CoreSchedule::Main` was explicitly used to get the schedule for the `OnUpdate` set. This can lead to failures or weird behavior if `add_state` is used with a differently configured `default_schedule_label`, because the other systems are added to the default schedule. This PR fixes that.

## Solution

Use `default_schedule_label` to retrieve a single schedule to which all systems are added.

2023-02-20 22:06:34 +00:00

src Use default schedule consistently in add_state (#7751 ) 2023-02-20 22:06:34 +00:00

Cargo.toml Release 0.9.0 (#6568 ) 2022-11-12 20:01:29 +00:00