MACRO: MacroBackerUpper—it's like Time Machine for your macro library

And 2.1 is out—if you have an older version, run the Update Check macro to download it, or just download from the link in the first post here. I found and fixed the two areas that were crashing the macro (hooray!), simplified the new user experience, and cleaned up some other stuff…

2.1 full release notes
  • New users have to answer only two questions to start: Backup folder name and location. The other settings are now optional on first run, which should greatly simplify the new user experience.

  • Fixed a mistake on my part that would cause the macro to fail if you renamed any macros or groups. (Long story short: I missed adding a new parameter to two calls to my SQL-handling subroutine that are needed to identify which database to work with.)

  • And fixed a similar mistake if you had groups named with a leading dot—they too would cause the macro to fail.

  • I misunderstood the %Trigger% token, and have now switched to the more-useful %TriggerBase% token. Translated to understandable, that means that if you've set the macro to only see the onscreen progress and summary dialogs when manually triggered, well, that should work now.

  • Fixed a bug that prevented the setting for the "macro done" notice (notification, window, or none) from working.

  • Fixed a problem with the Settings Manager where it didn't really quit when reloading, leaving some variables in a state that would then trigger some of the error trapping.

  • Corrected an incorrect find command in the step that verifies the backup folder was correctly named.

  • Removed a duplicate call to the First Run macro—thankfully, its macro reference was blank, so it wouldn't actually do anything.

  • Modified the (red text) warning in the First Run macro to make it clear it applies to those who have run older versions of the macro.

My thanks to everyone who reported issues and worked with me to help resolve them. MBU is, by far, the most complex macro I've ever written—it encompasses 1,233 separate actions spread across 26 macros, two separate databases, hundreds of SQL calls, and quite a few little Perl and shell scripts doing yeoman's work in the background. I'm thrilled with how it turned out, but that doesn't mean it came out perfect :).

(Thanks to ccstone's Count Actions in Selected Macro JXA 1.0.2 for making it reasonably easy to count all the actions in this macro!)

I try to test well on my Mac, but there are limits to both my time and ability—so your feedback has been invaluable in helping find and fix these issues when they occur.

-rob.

6 Likes