TL;DR: Set it so the Get Geometry input feeds into a GUID Param, then Elefront’s Extended Geometry param. This will reference the block and pass it into the rest of the script.
As @wim explained, Blocks are not native in Grasshopper, but of course Elefront is able to handle them, so if we can find a way to get the block into the script, we have a shot. In this case, the problem is that Grasshopper doesn’t realize it’s referencing a block, because it’s not set up for that. For example, if we have it print out what it thinks it’s operating on, we would expect to see Referenced Blocks:
However when you run this through Grasshopper Player, you get the a different result:
This tells us 3 things:
- Grasshopper IS reading in the two objects
- It knows that they are referenced objects
- It thinks they are Breps (so the Deconstruct Block Elefront component will fail)
This also checks out if you look at the options for the kinds of geometry that the Get Geometry input will accept:
Blocks are not listed, because they are not native to Grasshopper.
However, we know it’s properly getting the item in Rhino. So, it’s a bit of a hack, but since you are getting the object, you can get the GUID, then pass that into Elefront’s Extended Geometry parameter which will then convert the Guid into a Referenced Block before passing it into the rest of the script:
That said, I agree with @Japhy that it would be helpful to know what you are trying to do, because this is a bit round-about and there could be better ways to get what you’re after.