Dedicated user event API and editor UI #47
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, sending events into a graph from gameplay logic require manually adding an
EventQueueinput parameter through the animation graph player, and adding your event there. However, such a parameter would not get cleared every frame, so it would send the same events every frame until manually cleared.This PR adds a
send_eventAPI to the animation graph player that enables sending a single event that will get cleared at the end of the frame. It also adds some cleaner UI for sending events from the editor (for testing purposes), which allows you to save a few event types so that you can send them with a single click.