This is for all you guys that share macros.
Let's say I want to share a macro set, and it has options the user can change.
Up to this point, I've done something like including a macro named "User Options", which the user can change:
Obviously I call this from my main macro, to set all the options.
But what happens if I release an updated version of the macro set? I tell the user to delete the existing macros, and import the new version. Now they lose their changes to the User Options.
I could tell them to save their User Options, then replace them after the install. But what if the new version includes new options? They could wipe out the new options.
It seems to me there has to be a better way.
For example, they could create their own macro, which calls the main macro. Before calling the main macro, they could set whatever options they want. Then my "User Options" macro could look like this:
This is ideal, because they can keep their macro, and replace all the other macros.
But this leads to two questions:
- How do I explain this concept to them?
- How do I let them know what options are available?
I'm half tempted to create a dialog with all the options, and save their choices in a global variable. That way, when they install a new version, they don't lose their options. But this is problematic because there's no way to explain each option in the dialog, assuming it's a "Prompt for Input" action.
And creating a Custom HTML Prompt for this is not only time-consuming, but adds to the size of the macro set. I could solve the first problem by creating a Custom HTML Prompt that can be driven by config information. A list of variables, types, and help messages. But that could actually make the macro set even bigger (or maybe not).
Ideas? Thoughts?
