Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix typos in Event Handling and Sensors > Interaction handling #6

Closed
wants to merge 1 commit into from
Closed

Fix typos in Event Handling and Sensors > Interaction handling #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions website/docs/user_guides/rust/event_handling_and_sensors.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,10 +47,10 @@ same as for regular colliders as described in [that section](rigid_body_simulati
-->

## Interaction handling
I order to handle physics events, it is necessary to collect them using a structure implementing the `EventHandler` trait.
Because **Rapier** can be paralellized, this event handler must be `Send + Sync`. One such structure provided by `Rapier`
In order to handle physics events, it is necessary to collect them using a structure implementing the `EventHandler` trait.
Because **Rapier** can be parallelized, this event handler must be `Send + Sync`. One such structure provided by `Rapier`
is the `pipeline::ChannelEventCollector`. This event collector contains channels from the
[crossbeam crate](https://crates.io/crates/crossbeam). These channels will be populated with events during each called
[crossbeam crate](https://crates.io/crates/crossbeam). These channels will be populated with events during each call
to `pipeline.step`:


Expand Down