I have a feeling that the VIsualARQ tables are hugely under-utilized currently. They are simply marvelous as an idea, but the rigid implementation does not hold a candle to its potential. I mean, the idea of an automatically updating table that can be used on drawings as an object, is excellent, but it is so rigidly tied to certain types of VARQ objects. I see it as a much more universal Rhino tool.
I do not have a wish per se, but just writing out ideas on how I would like to use it. Currently, I’m creating tables through Gh as text objects and curves. Neat and lightweight to bake and to have, but a nightmare to update (well basically delete and re-generate).
- Tables should be in Gh as well
- _VaTableExport is super - What about _VaTableImport?
- Their editing and creation could be more generic, for instance, instead of categorizing Types, the input could be byName, byType (generic types; crvs, polys, etc.), byKey, byLayer, etc… To make it more of a Rhino tool, instead of “just” VARQ tool. Like a GeometryPipeline with a custom filter
- Double click to bring up an editor
- Automatic/Manual update
The whole table logic could also be implemented as a Gh-based object, as a Grasshopper style. There you could set up as an elaborate “Excel sheet” as you wish. The input and modification of “filters” should stay simple though.
The Rh7 Enhanced text fields have a little bit of the right directionality (Rhino - Enhanced Text Fields), but you can set it up only to count certain blocks. If you want to keep track of items and their quantities on a construction wall element, it doesn’t suffice.