-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Macro engine #2115
base: master
Are you sure you want to change the base?
Macro engine #2115
Conversation
This reverts commit e142c23.
Singletton pattern used to implement the macro recording / storing functionality
Problems with transitive dependencies
+1, I like the idea of tracing filters, layouts and appearance actions. This macro engine is a step towards a full execution history, which would allow undos as well. |
Thx @jbliesener , we appreaciate your feedback |
Thanks for the request, we will evaluate it. |
As a students of an Open Source projects course from University Pompeu Fabra (Barcelona), we have implemented a first version of a system that allows to record, edit and execute macros. We define a macro as a set of user actions that are stored to be easily executed at any time with a single click.
We've created a new menu in tool section that allows a user to:
The engine is currently working for actions in Appearance, Layout and Filters modules.