-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Move aabb gizmos to bevy_dev_tools
#12354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,10 +1,13 @@ | ||
//! This crate provides additional utilities for the [Bevy game engine](https://bevyengine.org), | ||
//! focused on improving developer experience. | ||
|
||
use bevy_app::prelude::*; | ||
pub mod aabb; | ||
#[cfg(feature = "bevy_ci_testing")] | ||
pub mod ci_testing; | ||
|
||
use aabb::AabbGizmoPlugin; | ||
use bevy_app::prelude::*; | ||
|
||
/// Enables developer tools in an [`App`]. This plugin is added automatically with `bevy_dev_tools` | ||
/// feature. | ||
/// | ||
|
@@ -35,7 +38,9 @@ pub mod ci_testing; | |
pub struct DevToolsPlugin; | ||
|
||
impl Plugin for DevToolsPlugin { | ||
fn build(&self, _app: &mut App) { | ||
fn build(&self, app: &mut App) { | ||
app.add_plugins(AabbGizmoPlugin); | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think, for now, we should hide it behind a feature and change it later when we create some other abstraction for toggling specific tools There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree. We have to create this abstraction soon, though, the amount of created features can be very high if we don't handle with care. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we can do There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've thought about it too, but wouldn't it then be impossible to change dev tools during runtime? I also thought about making a config as a resource but there might be a better way There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think there is a way at disabling this at runtime right now, at least not in the way we are currently doing There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes we can't add/remove plugins at runtime (see #11083), but maybe we could achieve something without plugins? I think we should create an issue regarding this to decide which direction we want to go for now |
||
|
||
#[cfg(feature = "bevy_ci_testing")] | ||
{ | ||
ci_testing::setup_app(_app); | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this probably makes mores sense as
aabb_gizmo
or something here :)