The BlockAttributeText -field does not accept [space] (" ") as a value in Rh8, and when " " is inputted, the last value remains visible. This works in Rh7.
Export to DWG only retains the top line of the multiline text - so text is trucated. This is the same in both versions. Key/values are retained. Export “2018 natural” (Rh8) and “2007 natural” (Rh7)
The space bug was introduced in Rhino 8 SR10 and is fixed in SR11. You should be able to download SR11 by switching your updates to Release Candidates.
Thanks @Trav ,
I can confirm that in SR11 [space] works as a value.
In DWG export, multiline BlockAttributeText does not export correctly. Multiline exports correctly outside and inside block, but not if it contains multiple BlockAttributeTexts.
I think that Rhino needs an ExplodeText command that it can explode multiple lines of text into single lines of text. Currently if you explode any text it will be turned into curves, and that is not going to help here. An ExplodeText would make the updates on this file easier.
Thank you for the detailed explanation @mary .
The possibility to explode multiline text into individual lines would be a welcomed addition, and something that I have searched as a command in the past. Would be rather easy to script something like that as well.
In the DWG export, in this case, the “explosion” to single lines should happen automatically in the background - the user should not have to worry, nor check the results for correctness afterward.
Hi @Toni_Osterlund,
I talked to the developers about this earlier in the week before I replied to you.
The chance of getting it wrong is very high. Block attributes have been in Rhino for two releases now. This is the first time it has been reported. All the tutorials I do, use separate line of text.
So…
Unless there is a huge up tick with this issue, the decision to allow the user to fix with a hopefully a new ExplodeText command is the plan.
Now this discussion is part of a searchable archive so anyone else having the issue, can see the recommendations.
@mary
I understand. But now that this is “shortcoming” is known, it should be made visible to the user.
The export dialog, letting the user know about the non-exportable objects, should also contain info about multiline BlockAttributeText export failing. This would give enough info to spot and correct the issue right away. It is easy to miss.
And currently, in my opinion, the dwg export is a bit too verbal. Each attribute is printed on the command line.
