release 4.2.3, fix bug in Morph effect

[sean]

Release 4.2.3. Fixes serious bug in Morph.

Gil has found a serious bug in the Morph effect.  He has code to detect if a conversion of old morph to new morph code should be executed. The internals of the Morph command was enhanced  over a month ago. One time code should have kicked in to change your old morph code the next time you opened a sequence. This bug is that the one time code got called multiple times. The effect? your morphs were possibly morphed.
How to fix? After installing new version, pull back an old version of your sequences (You are doing F10 every day?)
OR
just go and hand edit the morphs that dont look correct.
Note: This bug only affects those who use the Morph effect.

Thanks to Gil for finding and fixing the bug.


Latest releases are found at http://nutcracker123.com/nutcracker/releases/
Issue Tracker is found here: https://github.com/smeighan/xLights/issues

XLIGHTS/NUTCRACKER RELEASE NOTES:
--------------------------------
4.2.3  Aug 22, 2015
    -- bug(gil)   Version older detection code was wrong....this caused morphs to be converted when they shouldn't.
                  Also fixed morph corner 2b point graphic.

[colonelcline]

(You are doing F10 every day?)

It only backs up files under 10mb. In my case it only backs up the xml files. Is there a way internally to increase that? I use several external backups but some folks might not?

[JonB256]

It only backs up files under 10mb. In my case it only backs up the xml files. Is there a way internally to increase that? I use several external backups but some folks might not?

F10 only backs up the XML files. Do you have XML files > 10mb ??   I don't, so this isn't a problem. I certainly have FSEQ files > 10mb, but they don't need to be backed up since re-saving the associated XML will recreate them.