I think Fabian might be referring to exporting text fields separate from the geometry they are deriving their data from:
I agree that this is not very useful when for instance exporting for a layout file.
Maybe the mechanism should be to “bake” the text when exporting without the reference geometry.
This topic raises a question:
Is there an option to “bake” the text in any way? That would be a good feature to prevent unwanted changes to a textfield.
Say I have a floorplan, with the surface area’s annotated.
Yet in a second stage I want to delete the surface and replace them with their duplicated borders.
Then I would want to bake the textfields first to prevent loss of area annotation.
For V6 I think the textfield should be extended with functionality that:
- Warns for lost connections in textfields (much like we have a History warning system)
- Bakes the textfield information into regular text.
- Replaces geometry ID’s ( a way to edit a textfield and swap one connected object with another) That would make it a lot easier to quickly copy-edit textfield annotations.