This is a continuation of my feedback, with focus on the gen3 gh connectors.
Can you explain property sets (gen3) vs extend key/value (gen2). There is no effective way to create property sets now with a list of key and values. Requires me to manually name each key
I understand block support is still WIP. Currently the workaround to send blocks into from GH to Speckle is to use the Speckle Block Definition/Instance components provided in the Speckle 2 BIM. However from my knowledge, the Speckle 2 BIM components are not provided in the new gen 3 connectors. This means i have no workaround if i rely on gen3 connectors.
For the Speckle Group component in gen 2, it does not seem to work with ESO K/V component. It tells me that “1. Input object is not a Speckle object, nor can it be converted to one.” I would like to understand if the Group concept is going to be implemented in gen3?
Sync(Load) in gen3 not working same as Synchronous Sender in gen2. When automating the script with rhino.compute/ gh player, the synchronous sender in gen2 waits until the script completes before sending out, however it doesnt seem to be the case for gen3. This means that i end up with an empty output in speckle when using gen3 connector.
The keyvalue question has come up a few times: next-gen is designed to be more integrated with native components, so if you’re in Rhino 8 you can use the User Text component to work by keyvalue! In Next-Gen, Speckle properties from any application correspond to user strings in the Rhino context. See this thread for more details
Block support is coming! @bjoern is actively working on it now. You’ll be able to work with blocks with Next-Gen Grasshopper as if they are Rhino blocks (not related to BIM elements)
We haven’t planned supporting groups in GH, can you elaborate on the workflows you use them for?
Ah I see how it works. Will it be possible to group the properties into different dropdowns rather than everything under a single “properties” dropdown
Definitely looking forward to the block support. I will be sticking to gen 2 connectors until that is implemented. @bjoern Nested blocks would be very much appreciated as well.
Once the blocks are supported, groups wont be very necessary. I was just looking for alternatives to package my geometry together.
No, it’s not possible to create nested properties from GH currently - all Next-Gen data is using the properties field, but some applications do publish nested groups underneath the properties field. What’s your motivation for asking, is it for presenting the information in the viewer in a structured way or are you looking to do something else with nested props from GH?
I was just looking for alternatives to package my geometry together.
Some context here would help us a lot as well: do you specifically want instanced geometry, or just a way to attach multiple pieces of geometry to the same object? What’s your workflow here?
The example you showed is exactly what I would like to achieve. Presenting the information in the viewer in a structured way is definitely important. Being able to also retrieve these structured data to then create schedules (material/door/window/etc) in PowerBI or GH is also part of the workflow that I hope to achieve.
How can I create these nested properties for objects that I send through rhino/gh? Currently I am working with a BIM model in Rhino through the Visualarq plugin.
The sync publish issue is still in our QA backlog, but we did fixed a bug in release 3.4.0 that may have fixed it - if you’re able to give it a quick retest that would be helpful!
3.4.0 also comes with nested properties you can just pipe in the output of any property node as in input in another to nest them.
