7, 9, 12 and 13 to be able to rotate freely around the y axis at nodes 2, 3, 6, 7, 10 and 11 respectively. The last 2 conditions, for elements 12 and 13, doesn't give any problems, but the first 4 does.
Any help?
…
hi!
if i want to make a simple loop like the following:
int x = -3
while(x<7) {x=x+2}
is it possible to do with objects or should i try a VB component?
thanks for the support!
Z
e possible to change the component definition making possible to customize the number of outputs.Now Dispatch moves "true" values to A and "False" values to B
INPUT:
L (List to work on) -> 1, 2, 3, 4, 5, 6, 7, 8
D (Dispatch Pattern) -> True, False
OUTPUT:
A (List) -> 1, 3, 5, 7
B (List) -> 2, 4, 6, 8
Could it be possible/useful to modify it so it could dispatch items to several outputs, like:
INPUT:
L (List to work on) -> 1, 2, 3, 4, 5, 6, 7, 8, 9, 0
D (Dispatch Pattern) -> A, B, C
OUTPUT:
A (List) -> 1, 4, 7, 0
B (List) -> 2, 5, 8
C (List) -> 3, 6, 9
maybe I'm missing something and there's already a component with this function... I have been searching on the forum for half afternoon, but can't find anything about it!
Thank you!…
business that requires a lot of relationships between sliders.
For example if a Slider is giving a value between 3 and 7, a second slider should output between 2 and 10 in even numbers and a third slider only from 1 to 3 in 2 digits, while if the first slider goes above 7 the others also change accordingly to a relationship formula.
I know this can be done otherwise using other components but the beauty and functionality of a Slider with controlled inputs is that first: it makes it simple to achieve the relationship and second you have a perfect visual "input data display value" at hand.
One thing is to have a components modify a slider output by say -30% and one thing is to have the numbers on the slider giving you an exact display and control, or going from Integer to Floating: instead of using 2 sliders and let a user know when is one or the other.
Is like the weakest link of a strong chain.
I just find sliders to be beautifully simple and yet potentially very powerful tools if they could dynamically change and become little control panels in their cluster context.
This is one of the most desired function I am wishing for a long long time.
Marco…
cture, Rhino treats them as a single flat list. For example a surface can have 10 rows and 6 columns of control-points, resulting in a list of 60 points.
But 10 times 6 isn't the only way to get to 60. If you want to make a surface out of a list of 60 points, you'll also have to tell Rhino how those 60 points should be interpreted in terms of a grid. It could be 2*30, 3*20, 4*15, 5*12, 6*10, and all of the aforementioned products the other way around.
Sometimes there's only one way for a number of points to fit into a rectangular grid. For example if you provide 49 points, then 7*7 is the only way to make it work, but these cases are rare so we always demand you give us all the information required to actually make a rectangular grid of control-points from a linear collection.
As for "Why is it, sometimes we need to attach additional value into it?", this is usually because when you divide a domain or a curve into N segments, you end up with N+1 points. For example take the domain {0 to 5}, and divide it into 5 equal subdomains. You end up with {0 to 1}, {1 to 2}, {2 to 3}, {3 to 4} and {4 to 5}. However there are six numbers that mark the transitions between these domains 0, 1, 2, 3, 4 and 5. This is why you often have to add 1 to the UCount, because the number that controls the UCount often results in N+1 actual points.…
Added by David Rutten at 8:30am on December 25, 2014