2022-05-16 13:53:20 +00:00
|
|
|
//! Demonstrates the creation and registration of a custom plugin.
|
|
|
|
//!
|
|
|
|
//! Plugins are the foundation of Bevy. They are scoped sets of components, resources, and systems
|
|
|
|
//! that provide a specific piece of functionality (generally the smaller the scope, the better).
|
|
|
|
//! This example illustrates how to create a simple plugin that prints out a message.
|
|
|
|
|
2020-11-22 00:38:24 +00:00
|
|
|
use bevy::{prelude::*, utils::Duration};
|
2020-05-03 08:30:10 +00:00
|
|
|
|
|
|
|
fn main() {
|
2021-07-27 20:21:06 +00:00
|
|
|
App::new()
|
2020-11-03 03:01:17 +00:00
|
|
|
.add_plugins(DefaultPlugins)
|
2020-05-03 08:30:10 +00:00
|
|
|
// plugins are registered as part of the "app building" process
|
|
|
|
.add_plugin(PrintMessagePlugin {
|
|
|
|
wait_duration: Duration::from_secs(1),
|
|
|
|
message: "This is an example plugin".to_string(),
|
|
|
|
})
|
|
|
|
.run();
|
|
|
|
}
|
|
|
|
|
2020-05-16 07:27:30 +00:00
|
|
|
// This "print message plugin" prints a `message` every `wait_duration`
|
2020-05-03 08:30:10 +00:00
|
|
|
pub struct PrintMessagePlugin {
|
|
|
|
// Put your plugin configuration here
|
|
|
|
wait_duration: Duration,
|
|
|
|
message: String,
|
|
|
|
}
|
|
|
|
|
2020-08-08 03:22:17 +00:00
|
|
|
impl Plugin for PrintMessagePlugin {
|
2020-05-03 08:30:10 +00:00
|
|
|
// this is where we set up our plugin
|
2021-07-27 20:21:06 +00:00
|
|
|
fn build(&self, app: &mut App) {
|
2020-05-03 08:30:10 +00:00
|
|
|
let state = PrintMessageState {
|
|
|
|
message: self.message.clone(),
|
Replace the `bool` argument of `Timer` with `TimerMode` (#6247)
As mentioned in #2926, it's better to have an explicit type that clearly communicates the intent of the timer mode rather than an opaque boolean, which can be only understood when knowing the signature or having to look up the documentation.
This also opens up a way to merge different timers, such as `Stopwatch`, and possibly future ones, such as `DiscreteStopwatch` and `DiscreteTimer` from #2683, into one struct.
Signed-off-by: Lena Milizé <me@lvmn.org>
# Objective
Fixes #2926.
## Solution
Introduce `TimerMode` which replaces the `bool` argument of `Timer` constructors. A `Default` value for `TimerMode` is `Once`.
---
## Changelog
### Added
- `TimerMode` enum, along with variants `TimerMode::Once` and `TimerMode::Repeating`
### Changed
- Replace `bool` argument of `Timer::new` and `Timer::from_seconds` with `TimerMode`
- Change `repeating: bool` field of `Timer` with `mode: TimerMode`
## Migration Guide
- Replace `Timer::new(duration, false)` with `Timer::new(duration, TimerMode::Once)`.
- Replace `Timer::new(duration, true)` with `Timer::new(duration, TimerMode::Repeating)`.
- Replace `Timer::from_seconds(seconds, false)` with `Timer::from_seconds(seconds, TimerMode::Once)`.
- Replace `Timer::from_seconds(seconds, true)` with `Timer::from_seconds(seconds, TimerMode::Repeating)`.
- Change `timer.repeating()` to `timer.mode() == TimerMode::Repeating`.
2022-10-17 13:47:01 +00:00
|
|
|
timer: Timer::new(self.wait_duration, TimerMode::Repeating),
|
2020-05-03 08:30:10 +00:00
|
|
|
};
|
2021-07-27 23:42:36 +00:00
|
|
|
app.insert_resource(state).add_system(print_message_system);
|
2020-05-03 08:30:10 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
Make `Resource` trait opt-in, requiring `#[derive(Resource)]` V2 (#5577)
*This PR description is an edited copy of #5007, written by @alice-i-cecile.*
# Objective
Follow-up to https://github.com/bevyengine/bevy/pull/2254. The `Resource` trait currently has a blanket implementation for all types that meet its bounds.
While ergonomic, this results in several drawbacks:
* it is possible to make confusing, silent mistakes such as inserting a function pointer (Foo) rather than a value (Foo::Bar) as a resource
* it is challenging to discover if a type is intended to be used as a resource
* we cannot later add customization options (see the [RFC](https://github.com/bevyengine/rfcs/blob/main/rfcs/27-derive-component.md) for the equivalent choice for Component).
* dependencies can use the same Rust type as a resource in invisibly conflicting ways
* raw Rust types used as resources cannot preserve privacy appropriately, as anyone able to access that type can read and write to internal values
* we cannot capture a definitive list of possible resources to display to users in an editor
## Notes to reviewers
* Review this commit-by-commit; there's effectively no back-tracking and there's a lot of churn in some of these commits.
*ira: My commits are not as well organized :')*
* I've relaxed the bound on Local to Send + Sync + 'static: I don't think these concerns apply there, so this can keep things simple. Storing e.g. a u32 in a Local is fine, because there's a variable name attached explaining what it does.
* I think this is a bad place for the Resource trait to live, but I've left it in place to make reviewing easier. IMO that's best tackled with https://github.com/bevyengine/bevy/issues/4981.
## Changelog
`Resource` is no longer automatically implemented for all matching types. Instead, use the new `#[derive(Resource)]` macro.
## Migration Guide
Add `#[derive(Resource)]` to all types you are using as a resource.
If you are using a third party type as a resource, wrap it in a tuple struct to bypass orphan rules. Consider deriving `Deref` and `DerefMut` to improve ergonomics.
`ClearColor` no longer implements `Component`. Using `ClearColor` as a component in 0.8 did nothing.
Use the `ClearColorConfig` in the `Camera3d` and `Camera2d` components instead.
Co-authored-by: Alice <alice.i.cecile@gmail.com>
Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com>
Co-authored-by: devil-ira <justthecooldude@gmail.com>
Co-authored-by: Carter Anderson <mcanders1@gmail.com>
2022-08-08 21:36:35 +00:00
|
|
|
#[derive(Resource)]
|
2020-05-03 08:30:10 +00:00
|
|
|
struct PrintMessageState {
|
|
|
|
message: String,
|
2020-06-04 02:53:41 +00:00
|
|
|
timer: Timer,
|
2020-05-03 08:30:10 +00:00
|
|
|
}
|
|
|
|
|
2020-06-04 02:53:41 +00:00
|
|
|
fn print_message_system(mut state: ResMut<PrintMessageState>, time: Res<Time>) {
|
2021-03-05 19:59:14 +00:00
|
|
|
if state.timer.tick(time.delta()).finished() {
|
2021-04-22 23:30:48 +00:00
|
|
|
info!("{}", state.message);
|
2020-05-03 08:30:10 +00:00
|
|
|
}
|
|
|
|
}
|