11b41206eb
This updates the `pipelined-rendering` branch to use the latest `bevy_ecs` from `main`. This accomplishes a couple of goals: 1. prepares for upcoming `custom-shaders` branch changes, which were what drove many of the recent bevy_ecs changes on `main` 2. prepares for the soon-to-happen merge of `pipelined-rendering` into `main`. By including bevy_ecs changes now, we make that merge simpler / easier to review. I split this up into 3 commits: 1. **add upstream bevy_ecs**: please don't bother reviewing this content. it has already received thorough review on `main` and is a literal copy/paste of the relevant folders (the old folders were deleted so the directories are literally exactly the same as `main`). 2. **support manual buffer application in stages**: this is used to enable the Extract step. we've already reviewed this once on the `pipelined-rendering` branch, but its worth looking at one more time in the new context of (1). 3. **support manual archetype updates in QueryState**: same situation as (2).
70 lines
2.5 KiB
Rust
70 lines
2.5 KiB
Rust
use bevy_ecs::{event::Events, prelude::*};
|
|
|
|
// In this example a system sends a custom event with a 50/50 chance during any frame.
|
|
// If an event was send, it will be printed by the console in a receiving system.
|
|
fn main() {
|
|
// Create a new empty world and add the event as a resource
|
|
let mut world = World::new();
|
|
world.insert_resource(Events::<MyEvent>::default());
|
|
|
|
// Create a schedule and a stage
|
|
let mut schedule = Schedule::default();
|
|
|
|
// Events need to be updated in every frame. This update should happen before we use
|
|
// the events. To guarantee this, we can let the update run in an earlier stage than our logic.
|
|
// Here we will use a stage called "first" that will always run it's systems before the Stage
|
|
// called "second". In "first" we update the events and in "second" we run our systems
|
|
// sending and receiving events.
|
|
let mut first = SystemStage::parallel();
|
|
first.add_system(Events::<MyEvent>::update_system);
|
|
schedule.add_stage("first", first);
|
|
|
|
// Add systems sending and receiving events to a "second" Stage
|
|
let mut second = SystemStage::parallel();
|
|
second.add_system(sending_system.label(EventSystem::Sending));
|
|
second.add_system(receiving_system.after(EventSystem::Sending));
|
|
|
|
// Run the "second" Stage after the "first" Stage, so our Events always get updated before we use them
|
|
schedule.add_stage_after("first", "second", second);
|
|
|
|
// Simulate 10 frames of our world
|
|
for iteration in 1..=10 {
|
|
println!("Simulating frame {}/10", iteration);
|
|
schedule.run(&mut world);
|
|
}
|
|
}
|
|
|
|
// System label to enforce a run order of our systems
|
|
#[derive(SystemLabel, Debug, Clone, PartialEq, Eq, Hash)]
|
|
enum EventSystem {
|
|
Sending,
|
|
}
|
|
|
|
// This is our event that we will send and receive in systems
|
|
struct MyEvent {
|
|
pub message: String,
|
|
pub random_value: f32,
|
|
}
|
|
|
|
// In every frame we will send an event with a 50/50 chance
|
|
fn sending_system(mut event_writer: EventWriter<MyEvent>) {
|
|
let random_value: f32 = rand::random();
|
|
if random_value > 0.5 {
|
|
event_writer.send(MyEvent {
|
|
message: "A random event with value > 0.5".to_string(),
|
|
random_value,
|
|
});
|
|
}
|
|
}
|
|
|
|
// This system listens for events of the type MyEvent
|
|
// If an event is received it will be printed to the console
|
|
fn receiving_system(mut event_reader: EventReader<MyEvent>) {
|
|
for my_event in event_reader.iter() {
|
|
println!(
|
|
" Received message {:?}, with random value of {}",
|
|
my_event.message, my_event.random_value
|
|
);
|
|
}
|
|
}
|