12-27-2013, 11:16 AM
Hi Dean,
I got ahead of myself today and started up the Macro Editor prior to upgrading my development machine. There was no version checking, it let me get in and make changes with no warnings. After I realized what I had done I shut down the editor and then upgraded from 4.4.0 to 4.4.1. Much weirdness ensued after, things like I was not able to edit actions in an HTTP Trigger driver nor was I able to re-train the trigger. Shut everything down on the development machine rebooted it and re-updated CQC to 4.4.1 and everything now works the way it is supposed to.
You might consider putting in a version check on the macro editor to prevent the scenario I just went through. OTOH the likelihood of someone else doing what I just did are probably pretty small...
-Ben
I got ahead of myself today and started up the Macro Editor prior to upgrading my development machine. There was no version checking, it let me get in and make changes with no warnings. After I realized what I had done I shut down the editor and then upgraded from 4.4.0 to 4.4.1. Much weirdness ensued after, things like I was not able to edit actions in an HTTP Trigger driver nor was I able to re-train the trigger. Shut everything down on the development machine rebooted it and re-updated CQC to 4.4.1 and everything now works the way it is supposed to.
You might consider putting in a version check on the macro editor to prevent the scenario I just went through. OTOH the likelihood of someone else doing what I just did are probably pretty small...
-Ben
