algorithmic modeling for Rhino
Hi Stan,
the way to read a relative offset path is to append the items in the offset path to the original path. So if the offset path is:
{0;0;1}(1)
and you apply it to an existing path, say:
{0;2;0}(4)
you'll get:
{0+0; 2+0; 0+1}(4+1) which equals {0;2;1}(5)
There's no "A" or "B" placeholders in there like you'd get with the PathMapper. In fact, I always specifically prepend the sign of the offset, just to make it more obvious what's happening:
{0;0;+1}(+1)
If the new path doesn't exist within the data structure, then the wrapping logic comes into play as well.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
The whole point of the Relative Item components is to create data pairs. Therefore the data structure layout of both A and B outputs should be identical, otherwise there would be 'radicals'. The only difference between A and B, is which particular data item is stored at a specific location* inside the data tree.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
* a data location is defined both by the path (the curly bracket thing) and the index (the round bracket number).
Ah, Now I understand. Thanks for working this through with me.
Stan
I am certain I have not done a good job of explaining myself so... I can possibly address my findings by asking one question which should either confirm my suspicion of a bug or not.... What list can one expect get from the A output?
Sorry to be so unclear.
Stan
Ah, the data inside A is exactly the same as the data inside T.
Except when no matching relative item can be found (because wrapping has been disabled) in which case A will not contain that particular data items from T.
--
David Rutten
david@mcneel.com
Poprad, Slovakia
Welcome to
Grasshopper
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
Added by Parametric House 0 Comments 0 Likes
© 2024 Created by Scott Davidson. Powered by