Commands Send Event

An extension trait for Commands that allows you to send Bevy Events generically.

Version 0.4

Removed the niave retrieve-EventWriter-with-SystemState implementation. Now we just access the Events<T> resource directly.

• version >0.3 supports Bevy 0.7
• versions <0.3 support Bevy 0.6

Limitations

• Events won't be dispatched immediately, but at the next Stage boundary when the queued commands are applied to the World.

#

Usage

Add to your Cargo.toml [dependencies] section commands_send_event = "0.4"

then the send_event method is available on Commands:

```rust use commandssendevent::CommandsSendEvent;

[derive(Component)]

struct MyEventA(String);

[derive(Component)]

struct MyEventB(i32);

fn sender( mut commands: Commands ) { commands.sendevent(MyEventA("Hello, World")); commands.sendevent(MyEventB(42)); } The /examples folder has two examples you can run with: cargo run --example basic_usage cargo run --example schedule ```

0.2 update

Now there is also AnyEventWriter:

```rust use commandssendevent::AnyEventWriter;

[derive(Component)]

struct MyEventA(String);

[derive(Component)]

struct MyEventB(i32);

fn sender( mut eventwriter: AnyEventWriter, ) { eventwriter.send(MyEventA("Hello, World")); event_writer.send(MyEventB(42)); } ```

AnyEventWriter is a facade over Commands that implememnts SystemParam.

#

Notes

As an alternative, you can use commands.add to queue a closure: rust commands.add(|world: &mut World| world .resource_mut::<Events<_>>() .send(MyEvent) );