You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please explain.
I was experimenting with BackgroundAction syntax and I was thinking it might be a good idea to extend SubAction syntax to BackgroundAction's. Especially for the functions draw_grid and zero_lines.
If that is the case, it might make sense to have BackgroundAction only have access to functions like draw_grid and zero_lines and not as a general Action.
Describe the solution you'd like
What I would love to see as a user interface would be something like this:
Also, I am not sure if this should be a separate issue, but I would like to see the grid lines persist after their initial animation such that I could draw on top of them later.
Describe alternatives you've considered
Currently, this would be the way to invoke this functionality:
where appear can take some arguments like here :lr left -> right and :tb for top -> bottom and then this gets saved in the parent Action options or something such that the draw_grid function knows how to handle that :D
Then Action(1:60, draw_grid) might simply draw the grid for that many frames without any animation?
Is your feature request related to a problem? Please explain.
I was experimenting with
BackgroundAction
syntax and I was thinking it might be a good idea to extendSubAction
syntax toBackgroundAction
's. Especially for the functionsdraw_grid
andzero_lines
.If that is the case, it might make sense to have
BackgroundAction
only have access to functions likedraw_grid
andzero_lines
and not as a generalAction
.Describe the solution you'd like
What I would love to see as a user interface would be something like this:
Also, I am not sure if this should be a separate issue, but I would like to see the grid lines persist after their initial animation such that I could draw on top of them later.
Describe alternatives you've considered
Currently, this would be the way to invoke this functionality:
The text was updated successfully, but these errors were encountered: