got a slider give integers between -8~2, as right click slider cannot set the length of domain, and it cannot be smaller than 10 here.
If i change domain before setting the slider type, i can get a right slider. But change the upper to 5, the lower become -5 again. Double click on a slider is working wonderful, but i think right click should be useful as well.…
dimension of matrices must be identical) and division is the same as multiplication (dimension must be in the order of A(mxn)*\/B(nxk) where n is the common dimension): to divide one element by another you just multiply it by 1/value (part or all of the elements can multiply while part or all of the elements divide):
so for example matrix addition of matrices A(2x2): {2,-1}{1,2} and B(2,2): {3,-5}{4,-2} will result in matrix C(2x2):{5,-6}{5,0}. subtraction of those matrices will result in D(2x2): {-1,4}{-3,4}
Division of matrices A(2x2): {2,0.5}{2,4} and B(2x1) :{2}{2} will result in matrix C(2x1): {1+0.25}{1+2}={1.25,3}. Multiplication of those matrices will result in D(2x1):{4+1}{4+8}={5,12}.…
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
vector * number
8. number * point
9. point * number
10. complex * complex
11. colour * colour
12. colour * number
13. number * colour
--
David Rutten
david@mcneel.com
Seattle, WA…
Added by David Rutten at 10:39pm on November 12, 2010
the components seem to handle that like a list of lists, like a 2D array.
Say I send this 2x4 data to a curve divide, and it creates 10 points per each of 8 curves, then I feel like it should be outputting a sort of 3D array - 2 paths of 4 paths of 10 points, and I CAN still see the array structure in the param viewer. But I feel like it is outputting paths 20 paths of 5 point each. Is there are way to access the 2x10 stucture at this point?
(Manuel, I did just read your reply to my other post, and see that might be an answer to this, thanks)
Is everything pretty much handled as a 2D list of lists, and no 3D (no list of lists of lists)?
Are the tree logic components the key to getting the right 2D structure out of 3D (or deeper) structures?
Thanks!!!
Chris…
Added by Chris Wilkins at 9:57am on October 18, 2009