stand the way that GH manages collections (Lists and DataTrees) and then do whatever. 99% of issues that users have are due to poor knowledge with regard how to "sample" (and "manage") things in collections.
2. Read 1.
3. Next: At least 1Z definitions are available in this Noble Forum ... so get some and do something.
best…
Integer = 0 To 9
val *= 2
lst.Add(val)
Next
Since val is a ValueType, when we assign it to the list we actually put a copy of val into the list. Thus, the list contains the following memory layout:
[0] = 2
[1] = 4
[2] = 8
[3] = 16
[4] = 32
[5] = 64
[6] = 128
[7] = 256
[8] = 512
[9] = 1024
Now let's assume we do the same, but with OnLines:
Dim ln As New OnLine(A, B)
Dim lst As New List(Of OnLine)
For i As Integer = 0 To 9
ln.Transform(xform)
lst.Add(ln)
Next
When we declare ln on line 1, it is assigned an address in memory, say "24 Bell Ave." Then we modify that one line over and over, and keep on adding the same address to lst. Thus, the memory layout of lst is now:
[0] = "24 Bell Ave."
[1] = "24 Bell Ave."
[2] = "24 Bell Ave."
[3] = "24 Bell Ave."
[4] = "24 Bell Ave."
[5] = "24 Bell Ave."
[6] = "24 Bell Ave."
[7] = "24 Bell Ave."
[8] = "24 Bell Ave."
[9] = "24 Bell Ave."
To do this properly, we need to create a unique line for every element in lst:
Dim lst As New List(Of OnLine)
For i As Integer = 0 To 9
Dim ln As New OnLine(A, B)
ln.Transform(xform)
lst.Add(ln)
Next
Now, ln is constructed not just once, but whenever the loop runs. And every time it is constructed, a new piece of memory is reserved for it and a new address is created. So now the list memory layout is:
[0] = "24 Bell Ave."
[1] = "12 Pike St."
[2] = "377 The Pines"
[3] = "3670 Woodland Park Ave."
[4] = "99 Zoo Ln."
[5] = "13a District Rd."
[6] = "2 Penny Lane"
[7] = "10 Broadway"
[8] = "225 Franklin Ave."
[9] = "420 Paper St."
--
David Rutten
david@mcneel.com
Poprad, Slovakia…
Added by David Rutten at 6:26am on September 9, 2010
- I mean accurate ... unlike the image that you posted that displays sun related stuff (99%) whilst a tiny "dot" (1%) relates with the focus of interest.
BTW: sun is not "an atractor" since rays are // (therefor all these @$@% things rotate with the same angle ???)
…
s (and God knows how many in the next case) that's why (other than the colossal amount of time (for no reason) required for creating them ... try to bake them and measure the file size).
3 .Most non pros believe that the thing that matters the most in engineering is the geometry. Nothing could be further from the truth. Is about the 5% (complex real-life cases etc etc - but this one is very simple geometry wise and not that simple with regard the whole "ideal" AND effective strategy required).
4. So I've included in this Rhino file attached a small portion of your frames as input for the second C#: CAREFULLY study what it does and most importantly why: it gives you the clear indication about why you should attack this on an assembly/component basis by using instance definitions INSTEAD of recreating 14++ K "solids". The difference in performance is COLOSSAL, not to mention the baked Rhino file size.
5. Using instances is IMPOSSIBLE whiteout code (as is the case in 99% or real-life engineering tasks).
6. Geometry was never an issue on that one (is the 5% max of the whole puzzle no matter requirements you may have).
Bad news:
1. Zoom extends doesn't work after importing your data (maybe a NVidia Quadro K4200 driver issue - who knows?): use saved views stored.
So ...the choice is yours, best, Lord of Darkness…
whole mesh. So if you have a mesh with 100 vertices, face 1 might point to vertices (0,1,2,3) and face two can look like (100,1,2,99). This only means, that vertex 100 and 99 are connected with vertex 1 and 2 to form a face.
The face normal (inside/outside) is deteminded by vertex order. So if the mesh wraps around, you are bound to find some vertices traveres in reverse order. This in neccessary to have all faces point outward.…
u see around you they lack any zen: that allows the 1% to shine.
2. Each thing that you do/design never dies inside you: Let's call it an "event". The sum of them formulate you as an Engineer. If some "events" are faulty (or worst: shallow) your kaleidoscopic sampling is disturbed proportionally to the sum of the bad "events".
3. "Events" MUST withstand Time: there's nothing worst than fading reasons for doing this or that.
4. "I want" means nothing (anyone wants this or that, so what?). "I did it because" means - maybe - something.
5. Cost (and modesty) should be always your FIRST concern: forget form exploitation(s), new frontier(s) and other similar nonsense > they just yield another pointless waste of resources and guide you gradually into an amoral state of the worst kind: Remember > 1 dollar can save the life of one kid in Africa per day > in this context it's rather hard to justify ... well ... pretty much anything.
6. If you can do anything imaginable this means that you should do LESS other wise you'll find yourself trapped into a rabbit hole that has many entries but not a single #^%^# exit.…