Could there be a generic number input (or several using the little 'plus' buttons) to allow a variable (or variables) to be used in the component (x,y etc similar to evaluate function). I've seen workarounds for this which bypass the PM altogether, but it would be so much neater to contain it all in one? Could make it all powerful?
2) Medium
Disconnection and navigation:
a) Disconnecting a/several component(s) using just a straight drag onto a blank section of canvas. (Right click disconnect is a bit clunky if more precise when dealing with multiples, obviously retain this).
b) 'Charging' - when connecting two components that are miles away from each other, the hold-down and drag-pan approach can be tedious. Could charge-hold a connection (maybe a mouse-click + modifier) then be free to navigate to the target and 'discharge' the connection into it. A useful global zoom All and single click zoom back in shortcut could help with this. (think Mac Desktop: mission control)
3) Hard:
Ability to click GH geom in the Rhino viewport and highlight the corresponding component in GH. Where GH geom is overlapping, employ similar 'list-pick' to rhino; perhaps use with auto zoom/pan to relevant components in GH on highlight in list.
Keep up the good work
R
…
Added by Ralph Parker at 12:15pm on December 15, 2014
rce',)Failed to copy the object. Returning the original objects...This can cause strange behaviour!Duplicate surface name! Name is changed to: Overhang (roof)_DupDuplicate surface name! Name is changed to: Adiabatic walls_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_Dup_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_Dup_Dup_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_Dup_Dup_Dup_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_Dup_Dup_Dup_Dup_DupDuplicate surface name! Name is changed to: Adiabatic walls_Dup_Dup_Dup_Dup_Dup_Dup_Dup[1 of 7] Writing simulation parameters...Ground temperature data contains monthly average temperatures at 3 different depths .5 meters (1st)2 meters (2nd)4meters (3rd)respectively[2 of 6] No context surfaces...[3 of 6] Writing geometry...[4 of 6] Writing materials and constructions...[5 of 7] Writing schedules...[6 of 7] Writing loads and ideal air system...[7 of 7] Writing outputs......... idf file is successfully written to : c:\ladybug\unnamed\EnergyPlus\unnamed.idf
Analysis is running!...c:\ladybug\unnamed\EnergyPlus\eplusout.csv......
Done! Read below for errors and warnings:…
oes this but is rather very complex).
Anyway ... let's forget the quad mesh for the moment:
1. Create some patched brep (i.e. a "surface" with trimming info: this [a bit confusingly, he he] is NOT a surface ... because it's ... er ... a brep).
2. GH Patch is very temperamental and frequently omits trimming the brep especially against the inner loop curves. Nothing too serious mind (I have a C# that deals with this issue).
3. Using MeshMachine create the simplest tri-mesh possible.
4. Use K1 (or K2) for "relaxing" the mesh.
Note: steps 3-4 are covered with this very simple demo case attached (load R file first).
5.Now ... the yielding mesh is a tri-mesh ... and that's not what we want: Quadrangulate (what a word) the mesh (THIS is very tricky - I use also C# for that) and using mesh connectivity data (mesh faces/vertices are NOT following the "divide-a-surface" ordered way of doing business) make some geodetic truss.
more soon.
…
e fact. But why bother? You (with the proper ruthless training) you'll become the fittest bunny around. All signs certify that > you are a naturally born killer (but you don't know it - yet). Leave humanism for the losers.
2. For high class aesthetics glass is the only way. EFTE deteriorates over time > go for the eternal > avoid ephemeral. That said BirdAir does provide some stuff ... but glass is glass.
3. Light DOES not mean economical by any means. You'll discover that when ordering your proper Lamborghini (I do hope a Balboni: without ANY electronics > only for real men). Or you can try an ultra legera Ducati Panigale R (that costs 2 arms and 4 legs).
4. Cable design policy/adjustments/variants MUST take into account the fact that someone DOES the assembly manually: meaning that theory and reality differ vastly. One of these days a Skype session could teach you some stuff on that matter (mostly related with "deviations" from the ideally expected). My ultra complex connections posted from time to time are complex ... because they can handle any stupid action/mistake.
That said Ferrari stopped doing proper cars (blame decay) long time ago: Last standing hero > the notorious F40 (lethal). Other options: GTO 250 (immortal), LM 250 (THE racer), SWB 250 (for California cruising).
But ... you can try an Ariel Atom instead (make a good life insurance first). If you survive, that is. He, he.…
Mesh Colours]. It takes a single mesh and a list of colour values, one for each vertex (well actually it will cycle the colour list, but you want to provide one colour per vertex).
If you want to make an image (ie. an actual bitmap) by setting pixels, there are more efficient ways of achieving that, although that will require custom scripting and you won't be able to preview the data in GH or Rhino.
Finally, if you want to format a bunch of data into a comma separated list or some other kind of template, your best bet is usually the [Format] component. You'll need to increase the number of inputs to cater for all your data (6 in your case), decompose the points into XYZ values and decompose the colours into RGB values. Then you plug the x, y and z values into the 0, 1 and 2 inputs respectively, and the r, g and b values into 3, 4 and 5. Then the format you'll need will be something like:
{0}, {1}, {2}, {3}, {4}, {5}
Or, if you want to display all point coordinates with exact three decimals:
{0:0.000}, {1:0.000}, {2:0.000}, {3}, {4}, {5}
Or if you want to use semicolons to separate the point values from the colour values:
{0}, {1}, {2}; {3}, {4}, {5}
etc. etc.
…
upplied is of the wrong type, I would like a TypeError exception to be thrown.
However in this case (see 'incorrect' in pic below), it works even with incorrect types. For example I am feeding it curve objects (they are the same curves ) as arguments - this should give an error. However I think DA.GetData is casting the curve object to both an integer and a double resoectively for ID and S. This results in the command set_analog_out (48, 48.127...) instead.
How can I prevent this type conversion from occuring (if indeed that is the issue)? In RegisterInputParams, I am using i) AddIntegerParameter for ID and ii) AddNumberParameter for S.
My code for SolveInstance is:
int id = -1; double signal = double.NaN; if (!DA.GetData<int>(0, ref id)) { return; } if (!DA.GetData<double>(1, ref signal)) { return; } if (id < 0) { AddRuntimeMessage(GH_RuntimeMessageLevel.Error, "Check that proper id is supplied"); return; } if (!Rhino.RhinoMath.IsValidDouble(signal)) { AddRuntimeMessage(GH_RuntimeMessageLevel.Error, "Check that proper signal argument is given"); return; }
string URCommand = (StandardFunctions.SetAnalogOut(id, signal) + Environment.NewLine); DA.SetData(0, URCommand);
…