91b083bb05
# Objective Presently, it is possible to cause the `text_input` example to panic by pressing enter too quickly. This happens because, under these circumstances, the `listen_keyboard_input_events` system spawns multiple text entry entities where the `listen_received_character_events` system expects there to only ever be one. As this is an example this PR aims to highlight this risk and mitigate it. ## Solution Modify the example so that if a text entry has been spawned already during this run of the system then further Enter input events are ignored this run. |
||
|---|---|---|
| .. | ||
| char_input_events.rs | ||
| gamepad_input_events.rs | ||
| gamepad_input.rs | ||
| gamepad_rumble.rs | ||
| keyboard_input_events.rs | ||
| keyboard_input.rs | ||
| keyboard_modifiers.rs | ||
| mouse_grab.rs | ||
| mouse_input_events.rs | ||
| mouse_input.rs | ||
| text_input.rs | ||
| touch_input_events.rs | ||
| touch_input.rs | ||