Skip to content

Commit 82fa353

Browse files
committed
Fix references to old crate name in docs and examples
1 parent 23c393e commit 82fa353

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

crates/bevy_picking/src/backend.rs

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
//! This module provides a simple interface for implementing a picking backend.
22
//!
3-
//! Don't be dissuaded by terminology like "backend"; the idea is dead simple. `bevy_picking_core`
3+
//! Don't be dissuaded by terminology like "backend"; the idea is dead simple. `bevy_picking`
44
//! will tell you where pointers are, all you have to do is send an event if the pointers are
55
//! hitting something. That's it. The rest of this documentation explains the requirements in more
66
//! detail.
77
//!
8-
//! Because `bevy_picking_core` is very loosely coupled with its backends, you can mix and match as
8+
//! Because `bevy_picking` is very loosely coupled with its backends, you can mix and match as
99
//! many backends as you want. For example, You could use the `rapier` backend to raycast against
1010
//! physics objects, a picking shader backend to pick non-physics meshes, and the `bevy_ui` backend
1111
//! for your UI. The [`PointerHits`]s produced by these various backends will be combined, sorted,
@@ -158,8 +158,8 @@ pub mod ray {
158158
///
159159
/// ```
160160
/// # use bevy_ecs::prelude::*;
161-
/// # use bevy_picking_core::backend::ray::RayMap;
162-
/// # use bevy_picking_core::backend::PointerHits;
161+
/// # use bevy_picking::backend::ray::RayMap;
162+
/// # use bevy_picking::backend::PointerHits;
163163
/// // My raycasting backend
164164
/// pub fn update_hits(ray_map: Res<RayMap>, mut output_events: EventWriter<PointerHits>,) {
165165
/// for (&ray_id, &ray) in ray_map.iter() {

0 commit comments

Comments
 (0)