Block Origin : how does it works ?

Hello,

I don't understand how to use the Block origin parameter in the Define Block component.

Here is my example :

- I create the block (Define Block) starting with a GH geometry

- I place the block (Place Block) with 'Transform' doing nothing (null translation)... But i see the block instance in a another place and plane from the GH geometry. I expected that it would be in the same position of the GH geometry...

Thanks in advance

Attachments:

question pour forum define block block origin.gh, 158 KB
Forum question - block origin.png, 18 KB

Replies to This Discussion

Permalink Reply by Andrew Heumann on June 1, 2017 at 4:40am

Just like when you define a block in Rhino, you specify a base point (or plane in the case of Define Block). This represents the coordinate system of the block. When you insert the block with no transform (akin to the insert block command with insertion point set to 0,0,0) that coordinate system origin is placed at the world origin. So to get it back to the location where you defined it from, you don't need a "null" or identity transform - you need a transform mapping from the world XY (think of this as from the BLOCK's XY plane) to the plane you want it to be located at.

Permalink Reply by Jean-Louis Herman on June 1, 2017 at 7:14am

OK I understand now. Thank you !

By the way, i have a suggestion on the Place Block component :

It would be usefull to have an output on it (like Define Block), to do something when the block instance is done...

Permalink Reply by Andrew Heumann on June 1, 2017 at 8:02am

I will consider this - in the meantime, there's a kind of shortcut: you can create a fake "done" output by clustering the component with a boolean toggle connected with a cluster output - it will refresh its result every time the place block executes (though the value will always be true you'll get a new solution). This actually works to add an output to any component lacking one in order to force solution order.

RSS