ases where you have angled shades and the component is doing trigonometry to figure out how close the blinds could be to the glass without touching. I just re-wrote the code so that, now you cannot have the blinds closer to the glass than half of the blind slat depth, which seems to be the limit of what E+ will tolerate.
Also, E+ does not like it when you input blinds that are perfectly at 90 degrees so I changed the component to automatically write out shades at 89 degrees when you connect up 90.
Using the Shade geometry as context worked perfectly for me and I am not sure what was wrong in your situation.
See your working file attached.
-Chris…
g these times itself). If it works on selection alone, it would probably implement faster.
Theoretically, does this mean the total solving time of the definition is the 'chain of components' that takes the longest time? In the picture above, it would be the chain consisting 'point-curve-divideDistance'?
Because that still adds up only to 97%, I am assuming the Point and Slider component start solving in parallel, and the two Divide components also start solving in parallel?…
t it is rounded to 25, 100, 75. I've figured out the rounding portion, but when I plug the resulting list back into the custom preview, it doesn't recognize the data. I'm guessing it is because my rounded list is in curly brackets, whereas the unrounded data straight from the image sampler is not. How can I process this to remove the curly brackets?
Thanks,
Ryan
…
Added by Ryan Dirks at 5:20pm on September 18, 2014