@jari.huuskola Rhino 6 is in maintenance mode only at this point. All new features will be in Rhino 7.
Hi @Trav .
Is it possible to implement (I assume in v8 only) new, let’s say service, non-editable AttributeUserText field representing container of text-based objects (leaders, text objects)?
It’s like reversed task of current topic.
It’ll be auto-updated after text edit.
For example:
It will let user refer this attribute and create dynamic combinations, based on other text objects.
User text is always editable so I don’t foresee a non-editable reference.
As for passing around the text of a text object, I would suggest putting the text in Document User Text and then making the text object reference that text from the DocumentUserText fx function.