-
Notifications
You must be signed in to change notification settings - Fork 0
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
Preserving user modifications during updates #148
Comments
One related feature to this is #74 It should extract custom opcodes from one single file to separate folders where they could follow different update flow. |
User templates: #154 |
Thanks for the update! I've tried to add a custom template, and Yet what I would also like to have is a possibility to hide default templates if there are custom ones with the same name. For instance, I've changed The CLEO template story is the same as I told before: if one wants their own shared template, they'll have to manually edit all exclusive templates by either modifying or deleting them, yet these would be restored after a new version comes out, leading to new confusion and duplicates. So, in order to keep my own CLEO template, I had to name it other way and save as a custom template, which means I can't use “New CLEO script” but have to create an empty file and insert my template. All in all, the largest inconvenience for me is that you cannot just change/overwrite the default templates, since they always get restored. However, saving custom ones is a great step forward and a nice way to preserve and share template ideas, so I am grateful for this new feature! 👍 P. S. A stupid thought has crossed my mind that templates could be shared just like new themes, he-he. |
If you have some useful templates to share, submit a pull request in https://github.com/sannybuilder/data I will look into templates visibility. |
@VitalRus95 this has been implemented in v3.8.0-beta.0, please give it a try |
closing this discussion as templates have been implemented and opcodes are tracked in a separate ticket |
By the way, I noticed that templates are reset to standard ones after installing new versions, which is also an inconvenience, since I, for one, have my own CLEO template and slightly modified standard templates of conditions and loops. It would be cool to have them saved until a serious change is needed.
Originally posted by @VitalRus95 in #130 (comment)
The text was updated successfully, but these errors were encountered: