Skip to content

Finishing work for preemptively closed issue #2399 #2415

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 17 commits into from
Oct 14, 2024

Conversation

DragonMoffon
Copy link
Collaborator

No description provided.

einarf and others added 15 commits October 6, 2024 04:18
The names we had for the scale methods didn't feel right for arcade/python so they have been changed to be more readable.

While the concern about confusing the user is valid I think the change is worth it. During the interim before we do a larger re-write this is a nicer developer experience than using a method. Most developers set the sprite scale once, and then don't change it in the future.

the `isinstance` check for `AsFloat` is no-where near the cost of creating a vector.

In my ideal world sprite would not have a scale property at all, and instead scale is a method that changes the size of the sprite.
@DragonMoffon DragonMoffon changed the title Finishing work for premtively closed issue #2399 Finishing work for preemptively closed issue #2399 Oct 14, 2024
@DragonMoffon DragonMoffon merged commit 959d796 into development Oct 14, 2024
9 checks passed
@DragonMoffon DragonMoffon deleted the scale-tweaks branch October 14, 2024 21:52
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.

2 participants