diff options
| author | Alec Thomas <alec@swapoff.org> | 2016-02-05 23:57:14 -0500 |
|---|---|---|
| committer | Alec Thomas <alec@swapoff.org> | 2016-02-05 23:57:14 -0500 |
| commit | 089d26cfeec107847d779de77a58d6783f5ef88b (patch) | |
| tree | b00a9c59ae3e4d45afd830d43c1981cf6a33ce8a /README.md | |
| parent | 249d97a975d0ef97be66e3ce201f169e3a27101c (diff) | |
| parent | 4f67e896183c5d4f6ac32661d20ab715e5f6dbc8 (diff) | |
Merge pull request #129 from zackthehuman/entity_removal_on_destroy
Emit ComponentRemovedEvent<T> on Entity::destroy()
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -290,6 +290,7 @@ Several events are emitted by EntityX itself: - Event objects are destroyed after delivery, so references should not be retained. - A single class can receive any number of types of events by implementing a ``receive(const EventType &)`` method for each event type. - Any class implementing `Receiver` can receive events, but typical usage is to make `System`s also be `Receiver`s. +- When an `Entity` is destroyed it will cause all of its components to be removed. This triggers `ComponentRemovedEvent`s to be triggered for each of its components. These events are triggered before the `EntityDestroyedEvent`. ### Manager (tying it all together) |