-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Have a non layered action #24
Comments
Perhaps a better name for this might be "Extend Background Features" as it seems like the background should possibly be a special Action of its own with its own set of features. I think it makes sense to have that layered kwarg as a generic functionality for perhaps any Action. However, for the background Action, with how we are thinking about it, we might want to make it its own unique sort of Action. What do you think? It seems like there may be two problems here that are getting mixed together and by breaking them up, we might be able to better tackle them. |
Okay so we might want to have |
😂 I tried. How about "Make BackgroundAction"? |
And yea, I agree. That way, we can do unique things with |
How about |
I think I like |
Okay that one is merged to I'll close this. |
Currently we have the problem that the standard font color is black on a white background.
We can change the color in our
ground
(our normal name for the background function which is called as the first action) but it gets into its own layer such that the color is actually not "leaked" to the other layers.Unfortunately this is normally what the user expects. It's quite easy to have a keyword argument for this to say:
(maybe there is a better name for it @TheCedarPrince ? )
and then everything inside that action is available in the outside world. This way it's also possible to make a shift of the coordinate system there if one doesn't like to have the origin being in the middle.
The text was updated successfully, but these errors were encountered: