I used Elefront in Rhino 7 to be able to query objects through Worksessions, and it worked like a charm. It is still workin in Rhino 8, but they are not then references as model objects but as pure “Elefront” objects.
Now that I am migrating to Rhino 8, i want to use the Native query component instead, but i can´t seem to be able to query the object when it is in a worksession. It works fine if the object is in the active document but i cannot seem to be able to query that object or select it as a model object if it is in a worksession.
The only workaround is to import and then filter with might get extremely heavy and complex as our workflow request to query objects from multiple files at once. Any better solutions?. Any better solutions?
Well actually its not only about the filtering being heavy but also about being able to query simultaneously objects from different documents in a batch manner instead of having to import every document separately. So The size of the file does not matter that much. Ill edit the question.
But yes, when importing a file containing a relatively decent model, it took 58s. I need in some scripts to import data from up to 10 different files, so it will quickly not be usable anymore. The geometry is already loaded in the worksession, i dont want to have to reload it again in my grasshopper
Okay thanks!
So im guessing from your answer that there is currently no way of doing what I want with worksessions and Native grasshopper components. I guess that feature will not come in the coming weeks ? (Doing project setup at the moment so need to decide on the practice for it)
That’s correct. This item is currently on the “Future” list, so, at this point this is not something that is considered for Rhino 9. Of course, that might change. Worksessions do not exist on the macOS version of Rhino, and that might have an impact on the prioritization of this request.
-wim
