(Edit 2016/05/19 12:39 CST: Replaced macro file with a properly named one. The macro group will import disabled for safety, and the user must manually enable both the group and the macros in the group. -ccs)
If you post more than one version of a macro it’s a good idea to give the file a version string.
It’s not a bad idea to put an attribution comment in the macro either.
Usually when I change a one of my already posted macros I edit the original post and then post a new blurb like “Macro in post #1 updated 2016/05/19 15:52 CST”. That makes sure the forum’s email system pushes out a notification (which it does NOT do when you edit a post).
Good idea about the posts. I was trying to sneak in the new version, with its minor changes, before anyone downloaded the old :-)…
I’ve been putting attributions in a macro that describes the whole group. Sounds really tedious to put attribution in every Macro, though it would be easy enough to have a macro that creates the new macro and adds the attribution to it. Actually, I have something like this that creates a new macro and adds a keystroke trigger to it, ready for me to type the keystroke.
It just occurred to me that maybe not. I was assuming the group would remain intact, but of course users are free to move macros to other groups. In the case of my Mouse Positioning group that wouldn’t make sense, but if the group were a mixed bag of macros, each one should have an attribution. I guess the same goes for versions. Ugly.
I just (!) realized that there is an entire Wiki page carried over from the old KM Wiki documenting these macros in detail. I would also like to point out that although the keyboard shortcuts all use the extended keyboard keypad, one could develop a scheme that used the main keyboard. If you do, please let me know about it.