forked from bevyengine/bevy
-
Notifications
You must be signed in to change notification settings - Fork 0
/
removal_detection.rs
75 lines (67 loc) · 2.84 KB
/
removal_detection.rs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
// This example shows how you can know when a `Component` has been removed, so you can react to it.
use bevy::prelude::*;
fn main() {
// Information regarding removed `Component`s is discarded at the end of each frame, so you need
// to react to the removal before the frame is over.
//
// Also, `Components` are removed via a `Command`. `Command`s are applied after a stage has
// finished executing. So you need to react to the removal at some stage after the
// `Component` is removed.
//
// With these constraints in mind we make sure to place the system that removes a `Component` on
// the `CoreStage::Update' stage, and the system that reacts on the removal on the
// `CoreStage::PostUpdate` stage.
App::build()
.add_plugins(DefaultPlugins)
.add_startup_system(setup.system())
.add_system_to_stage(CoreStage::Update, remove_component.system())
.add_system_to_stage(CoreStage::PostUpdate, react_on_removal.system())
.run();
}
// This `Struct` is just used for convenience in this example. This is the `Component` we'll be
// giving to the `Entity` so we have a `Component` to remove in `remove_component()`.
struct MyComponent;
fn setup(
mut commands: Commands,
asset_server: Res<AssetServer>,
mut materials: ResMut<Assets<ColorMaterial>>,
) {
let texture = asset_server.load("branding/icon.png");
commands
.spawn(OrthographicCameraBundle::new_2d())
.spawn(SpriteBundle {
material: materials.add(texture.into()),
..Default::default()
})
.with(MyComponent); // Add the `Component`.
}
fn remove_component(
time: Res<Time>,
mut commands: Commands,
query: Query<Entity, With<MyComponent>>,
) {
// After two seconds have passed the `Component` is removed.
if time.seconds_since_startup() > 2.0 {
if let Some(entity) = query.iter().next() {
commands.remove::<MyComponent>(entity);
}
}
}
fn react_on_removal(
mut materials: ResMut<Assets<ColorMaterial>>,
removed: RemovedComponents<MyComponent>,
query: Query<(Entity, &Handle<ColorMaterial>)>,
) {
// Note: usually this isn't how you would handle a `Query`. In this example it makes things
// a bit easier to read.
let (query_entity, material) = query.iter().next().unwrap();
// `RemovedComponents<T>::iter()` returns an interator with the `Entity`s that had their
// `Component` `T` (in this case `MyComponent`) removed at some point earlier during the frame.
for entity in removed.iter() {
// We compare the `Entity` that had its `MyComponent` `Component` removed with the `Entity`
// in the current `Query`. If they match all red is removed from the material.
if query_entity == entity {
materials.get_mut(material).unwrap().color.set_r(0.0);
}
}
}