Sean Meighan
Welcome => Latest xLights/Nutcracker software => Topic started by: sean on April 07, 2016, 11:41:48 PM
-
Release 2016.18, many bug fixes.
I accidentally deleted 2016.17. I am not going to put it back up since it had some major bugs. Everyone should go to 2016.18
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.18 Apr 7, 2016
-- bug (gil) Fix bug when Papagayo timing was collapsed and selected grid cell selection wasn't working.
-- bug (gil) Fix Delete key operation so it doesn't do a Cut unless Shift is pressed.
-- bug (dkulp) Fix shift-del/ins on LayoutPanel as well
-- bug (dkulp) Fix "individual start channel" calculations
-- bug (dkulp) Set the buffer size correctly for candycanes. Fixes #521
-- bug (dkulp) Find a solution to some crashing in release builds
-- bug (dkulp) Remove model properties dialog and model list dialog
-- bug (dkulp) Fix crash in editing groups
-
I'm seeing problems with Text again. Was working in 2016.17, now gone in 2016.18
wxwidgets?
When I open a sequence saved in a prior version, the text displays ONCE, then never displays again (I'll assume it disappears after an auto render)
-
I'm seeing problems with Text again. Was working in 2016.17, now gone in 2016.18
wxwidgets?
When I open a sequence saved in a prior version, the text displays ONCE, then never displays again (I'll assume it disappears after an auto render)
Argh... I moved a platform specific setting out of a header and into the cpp file, but messed it up while testing some other things.
Windows has a very different Text rendering path than we use on the other platforms. I haven't been able to get the windows stuff working during the effect render. However, on my OpenGL 3 branch, I DO have windows text working with the wxGraphicsContext stuff so I do know it works, just need to figure out what the difference is.
-
Cool. It is listed as Beta!