[BUGFIX] Fix the instrumental selector being spammable #3866
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.
Does this PR close any issues? If so, link them below.
Fixes #3562
Briefly describe the issue(s) fixed.
CapsuleOptionsMenu
has its own method of handling inputs, independent ofFreeplayState
. This, in turn, meant that inputs were still enabled even AFTER selecting a song.This PR adds a Boolean called
busy
. This pretty much acts the same as the one inFreeplayState
.This is sort of a janky solution, but you can't really do anything much on the Freeplay side since
busy
is enabled to preventFreeplayState
from accepting inputs while the Instrumental Selector is open (unless you like... made a new boolean to check if the instrumental selector is open or something lol).Something to note
The arrows in the Instrumental Selector (
InstrumentalSelector
) can still be controlled, however, this is purely a visual thing.I tried tackling the issue before opening this PR, but I couldn't really figure out a solution without it being a mess.