Skip to content

Conversation

@Arecher
Copy link
Contributor

@Arecher Arecher commented Nov 7, 2025

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.

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...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant