Working with parametric and non-parametric objects
One of the strengths of RhinoParametrics is that it can use parametric objects within a standard Rhino modelling process, but also the opposite, meaning it can integrate non-parametric objects in a parametric modelling process.
To stop parametric mode simply close the plug-in (tree dialog). Rhino commands will then function as always, while parametric objects remain visible and available.
|
|
The example to the left shows that there is however a caveat in editing a parametric object with standard Rhino functions: modifications may be altered or lost if that object is later re-generated via the associative parametric process.
|
If work carried out in standard Rhino mode is to be preserved, it is better to make a copy of the parametric object, and then to use this copy (as opposed to using the original parametric object). In fact, making a copy with standard Rhino commands effectively breaks the parametric links.
To use a non-parametric object during a parametric session, it needs to be recognised by the parametric engine. This is done using the Link tool, which will work on any Rhino object, whether it has been created using Rhino commands or imported (ex. an iges import).
|
|
In the example to the left, a hull is being sectioned using a parametric plane. The surface was imported, and is not recognised by RhinoParametrics, hence it cannot be selected. The Link tool adds the object to the parametric session, after which the intersection will be recognised and the ensuing section can be computed.
|
The step 15 of this documention show diffrent exemple of the use of parametric and non parametric objects. |