2016.16 xLights released
Daniel Kulp has been busy fixing bugs that caused crashes.
There also was an issue where the scroll bar in the SEQUENCER tab was not smoothly scrolling through the waveform. That is fixed also.
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:
--------------------------------
2016.15 Apr 2, 2016
-- bug (dkulp) Fix icicle off by one
-- bug (dkulp) Fix some scrolling on windows issues
On Mac, the Test panel checkboxes don't work,
use double click action to simulate
-- bug (dkulp) Fix issue with single lines being clicked on too easily
-- bug (dkulp) Fix crash if a view contains models that no longer exist
-- bug (dkulp) Fix crash when clicking on checkbox in model list if no model is selected
-- bug (dkulp) Fix crash on import if source strands aren't in the source sequence
smeighan wrote:2016.16 xLights releasedDaniel Kulp has been busy fixing bugs that caused crashes.
There also was an issue where the scroll bar in the SEQUENCER tab was not smoothly scrolling through the waveform. That is fixed also.
Just out of curiosity....when a fix is implemented to solve issues like scrolling....would it be advisable to go back and render old sequences or is that scrolling just just an issue of the preview not scrolling? Or put another way. Does something like scrolling show up in the actual display or only in previews?
Thanx....
Prevuews should match what will go out to lights. You are editing,
Move things change sliders u see changes in SEQUENCER window. When u press save everything is written to fseq file . Fpp or xlights just reads fseq file.
So, if we have a bug and u pressed save, the fseq is not correct. U should open old sequence and just press save.
Sent from my iPhone using Tapatalk
Thanks Sean....that's helpful to those of us who are software challenged and don't fully understand the protocols behind the scenes. :biggrin2:
Since I'm not sure when one of these fixes impacts older sequences....I just made a note to self.....Prior going live for the season go back and open/save all the older sequences....just in case.....
another case of needing a re-save: if you change channels in any of your models. Last year i increased the number of arches I had from 12 to 15. This change caused starting channels of other models to change. My old fseq files did not know about the new channel layout. I went into my 11 sequences,
1) Opened them, 2) Saved them, 3) Go to next sequence
Now all the new fseq files were correct

