Fix "Send to new SlicerT instance" not sending to Pattern Editor#8339
Merged
rubiefawn merged 2 commits intoLMMS:masterfrom May 4, 2026
Merged
Fix "Send to new SlicerT instance" not sending to Pattern Editor#8339rubiefawn merged 2 commits intoLMMS:masterfrom
rubiefawn merged 2 commits intoLMMS:masterfrom
Conversation
Contributor
|
I was able to replicate the issue on the latest nightly version. I have tested this PR and can confirm it fixes the issue |
rubiefawn
approved these changes
May 4, 2026
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
3 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.
Currently, right-clicking on a sample in the sidebar and clicking "Send to new SlicerT instance" under the Pattern Editor section will always create the instance in the Song Editor, rather than the Pattern Editor like it suggests. This PR fixes this.