Open
Conversation
As far as I could see it does not include any parameters. I'm unsure about the new UI markers and whether they would be required here. I also just noticed this feature is still in beta, which might be why it wasn't in the documentation yet. But since I had already written it down anyway, might as well offer it up!
Added a note on how Range.layers seems to be sorted, since it was surprising to find the order does not match the order layers are usually presented (such as in sprite.layers or layer.layers), and does not follow the next most logical assumption, that they are presented in order of selection. I did some testing to determine that they are added in chronological order, but this could be coincidence if they are added in a random order instead.
…anch Added this one to the main branch a few days ago, so when I made the branch for the other change, that commit was mistakenly included too...
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
1 participant
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.
Added a note on how Range.layers seems to be sorted, since it was surprising to find the order does not match the order layers are usually presented (such as in sprite.layers or layer.layers), and does not follow the next most logical assumption, that they are presented in order of selection.
I did some testing to determine that they are added in chronological order, but this could be coincidence if they are added in a random order instead.