(fix) Looping: reset loop_end_pos on eject #12224
Merged
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.
Just a quick test if this fixes #12223
It works as expected, but let's run the tests.
In theory:
On eject,
loop_in_pos
was just reset (beforeslotLoopEndPos
is called) so this eval would always be true, regardless the invalid requestedloop_end_pos
.Fall through here and set
loop_end_pos
to -1 a few lines below.This code hasn't changed for very long, but maybe the callers?