Sean Meighan
Welcome => Latest xLights/Nutcracker software => Topic started by: sean on July 08, 2015, 01:34:18 AM
-
This release is the accumulation of content over the last week while I was on vacation.
Thanks again to Gil.
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.1.10 Jul 8, 2015
-- enh(gil) Add preview of image to the Effect Assist window for Pictures effect. More to come for this effect.
-- bug(gil) Selecting a single cell with any drag movement of the mouse was causing invalid effect end time when placed.
-- enh(gil) Add SaveAs to the File menu.
-- bug(gil) Fixed effects dropped on grid were not previewing.
-- enh(gil) Update View -> Windows so that Perspectives, and Display Elements windows work and add Effect Assist Window.
-- enh(gil) Add settings options for how the effect assist window behaves.
-- enh(gil) Added new panel to help in defining Morph positions. Will be expanded for other uses later.
-- enh(gil) Automatically initiate Render All after adding or modifying data layers when dialog is closed to remove confusion.
-- enh(gil) Add ability to Delete Views.
-- enh(gil) Allow timings to be added/removed from views. This info remains local to each sequence not stored as part of the view
since not all sequences have the same timing names.
-- bug (sean) Fix README.windows that got overwritten. These are instructions for compiling our code under windows
-
Gil, the morph effect assist is nice! It looks like it only works on models, not groups. Am I correct on this?
-
Actually I didn't try it on groups. I'm calling the model class to get the dimensions of the model and I'm not sure if a model group is returning the correct values. What do you see? Does the window just show blank or is the model not the correct size? One thing I was thought was cool is how if you drop a morph on a model you really get to see the size of the internal representation. I had some custom model candy canes that I discovered accidentally had a height of 50 when they were only 8 pixels tall so I was alerted to go fix them.
-
Phrog, your observation is correct.
-
What do you see? Does the window just show blank or is the model not the correct size?
It's blank.
Still, for the model, very nice addition.
James
-
Ok I'll have to see if there's an alternate way for me to read the dimensions of a model group. I think it would be a good indicator for folks to see the size of the group model because then you really know the size of the canvas the effect is being painted on.
-
I agree. Thanks Gil.
-
Gil, the morph effect assist is nice! It looks like it only works on models, not groups. Am I correct on this?
So what's happening here is the model groups were like 400x400 pixels. So I was getting the correct size it's just that when I calculated cell size for my grid the result was less than 1 so you got a 0x0 grid. I try to fit the entire grid into the view. I guess I could put a minimum cell size in there and then the scrollbars would activate. It won't be as easy to work with the window using scrollbars but at least you will see something. Dan has an update coming where you will be able to make the model group canvas smaller so that it may better fit the models in the group.
-
So what's happening here is the model groups were like 400x400 pixels. So I was getting the correct size it's just that when I calculated cell size for my grid the result was less than 1 so you got a 0x0 grid. I try to fit the entire grid into the view. I guess I could put a minimum cell size in there and then the scrollbars would activate. It won't be as easy to work with the window using scrollbars but at least you will see something. Dan has an update coming where you will be able to make the model group canvas smaller so that it may better fit the models in the group.
Well, if you maximize the window, the 400x400 grid would likely show up.
Also, if you flip to using doubles/floats for the rendering, that would be another big help, particularly for those of us on Retina MAC's where "1" is really two pixels. For us, the smallest unit could be 0.5x0.5. That said, I think I'd prefer the grid to start representing 2 rows or 3 rows or something once the width/height is over 100 or something. Since the Morph values are integers from 0-100, having smaller subdivisions won't really buy anything.
-
Sounds like my ToDo list just got longer. :)
-
Just a side observation. Once you get above 100 columns or rows the morph can't be placed on every single spot. It would need to be reworked so that the value had more resolution.