On Feb 17, 11:39 am, PJ <[email protected]> wrote: > The chief difference > in this case specifically is that in Rhinoscript, your geometry > variables are actually only strings that reference the objects > themselves, which you pass into functions (as in Rhino.DoSomething > (...)) to tell Rhinoscript how to modifiy the geometry.
That is the only real problem we have here. It is possible for VB.NET and RhinoScript to communicate on some level (the RhinoScript GDI extension plugin proves this readily enough), but the geometry problem PJ mentioned cannot be solved. Rhino5 will have many new functions in the SDK that are similar to the RhinoScript functions, so at least the transition will become easier, but you'll have to transfer if you want to write scripts in Grasshopper. -- David Rutten [email protected] Robert McNeel & Associates
