Fix BlendSpace point insertion shift at a specific index#119069
Merged
Conversation
BlueCube3310
approved these changes
May 10, 2026
Contributor
BlueCube3310
left a comment
BlueCube3310
left a comment
There was a problem hiding this comment.
Tested, this fixes issues with the last node disappearing after undoing removing other nodes. The changes make sense to me
Contributor
|
Thanks! |
This file contains hidden or 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
4 participants
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.
Split from #119029
The shift loop must start from
blend_points_used, which is the first free slot, notblend_points_used - 1, which is the last occupied slot. Otherwise, the last shifted point is overwritten instead of preserved.For example inserting
Bat index1into[A, C, empty]should result in[A, B, C]but currently it is[A, B, empty]