-
Notifications
You must be signed in to change notification settings - Fork 332
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
Add .rgb properties + tests for Color, Sprite, and BasicSprite #2060
Conversation
The GitHub basd tests / Code inspections step is failing on GUI / Text pyright issues as it has been recently. |
* Updated the color setter so that it does not change the current alpha * Updated it to check for use arcade.Color * Added an isintance check to the len3 check and moved those before the len4 check. So now if the user does a tuple of 3 (ie (255,255,255)) or uses the arcade.Color type (i.e. arcade.Color.BLACK) it will just reuse the old alpha. * Demo 1 * Added deeper RGB class * cleaned up RGB
b358a24
to
bf84bf1
Compare
TL;DR: This is ready to review. The recent force-push is a rebase onto development to get #2062's pyright fixes. |
In regards to my previous merge request, should I close it or is there something still relevant about it? |
@FriendlyGecko TL;DR: Don't delete the branch yet. We split the types module recently in #2065. That makes it easier to do future color improvements, but they'll probably have to wait till 3.1+ at the earliest. Before we do more with color, we first have a bunch of other things to do:
After 3.0, we might be able to start improving color types further. |
Changes
To the old PR:
Supersedes #1970 by:
To Arcade
Closes #1838 (Marked as 3.0 Mandatory) by:
.rgb
syntactic sugar property toColor
.rgb
property toBasicSprite
and subclasses:BasicSprite.color
The groundwork for this was handled by #2029.
Remaining questions
.color
?