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

Disabling InputMaps for inactive states #41

Closed
huhlig opened this issue Jan 20, 2022 · 2 comments
Closed

Disabling InputMaps for inactive states #41

huhlig opened this issue Jan 20, 2022 · 2 comments
Labels
blocked Nothing to do yet documentation Improvements or additions to documentation
Milestone
0.1

Comments

@huhlig
Copy link
Contributor

huhlig commented Jan 20, 2022

What problem did the developer encounter?

Looking for how to disable handling inputs for states/entities not currently active without removing components.

What was the fix?

Unknown

How could this be better documented?

Currently Undocumented.
@huhlig huhlig added the documentation Improvements or additions to documentation label Jan 20, 2022
@alice-i-cecile
Copy link
Contributor

This is mostly blocked by bevyengine/bevy#2160. Ideally we'd be able to just configure all of the input map plugin systems to run in the given state. bevyengine/rfcs#45 will largely resolve this.

@alice-i-cecile alice-i-cecile added the blocked Nothing to do yet label Jan 22, 2022
@alice-i-cecile alice-i-cecile added this to the 0.1 milestone Jan 23, 2022
@alice-i-cecile
Copy link
Contributor

Workaround created!

Use InputManagerPlugin::run_iff_state when adding your plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Nothing to do yet documentation Improvements or additions to documentation
Projects
None yet
Milestone
0.1
Development

No branches or pull requests
2 participants
@huhlig @alice-i-cecile