I use layout templates automatically populated with text fields containing several DocumentText fields containing global project info such as a client name, broader project information and then supported by individual drawing details:
This is fine for work within Rhino, however whenever I need to export as DWG for a client or for colleagues that don’t use Rhino these fields are exported literally. That is, when re-imported to Rhino they work as fields (albeit with missing document info) however as DWGs they no longer parse as fields for obvious reasons.
Now, is it possible to script this as a “pre-export to DWG” to housekeep these values, baking them in so that DWGs display correctly? In an ideal world the export function would have option to bake field values in purely for the purposes of the export function, however I can’t see that being high on the list of functionality changes for future versions. I very rarely work in the scripting languages available, but this seems like it might be an ideal candidate for one…even if it would be more one-way than as a function of the export path.
Any ideas or suggestions? Let me know if I missed some detail about what I mean…thanks!