Rhino 8 - text entity deconstruction issues

Hey all,
I scratched my head over this for quite some time until I finally figured out what is happening.
Not sure if that should be called a bug, but to me it appears as non-intuitive behavior at least.
The issue is following:

When text entity is created and for further operations with it we need to extract some of its properties (what I call “deconstruction”), then the properties coming from Text settings (Te) are always when the annotation style settings were not overridden.
Example down below - I create entity using predefined annotation style with text height 3. When I deconstruct the text entity, I would expect that the Th value is 3, but it is . However, when I override Th setting when the entity is being created, deconstructed Th value corresponds to the override. It’s the same situation with vertical/horizontal alignment (Va/Ha) for example.

Not sure if this behaviour is intended, I would expect Text settings (Te) to always expose actual settings of the text, no matter where they came from (override or annotation style).
In current situation, if I want to make my script snippet universal, I would have to combine extracted values for all properties from Annotation style and Text settings to ensure I always get value, because using Text settings only I risk getting nulls once the Text settings remain at default values.

I changed the topic category to Grasshopper.

And I rebuilt your definition and can’t see the same behaviour like you.

Rhino 9 WIP here…

text-entity_deconstruct.gh (14.2 KB)

Hey Martin,
that probably means that this is Rhino 8 issue only. I copied your setup reading the height from Annotation style and still same issue. So the solution will be to upgrade to Rhino 9? :smiley:

We are currently on Rhino 8 SR20

I also just opened my definition in the most current Rhino 8 and now I see the same as you.

That is unfortunate (for us). We probably won’t be able to upgrade anytime soon. At least we now know that the issue is fixed for the future, thank you for that information :slight_smile: It is not a huge issue, I am just loosing some time doing seemingly pointless comparisons, but yea, we can deal with it :smiley:
Do you think there is any chance that this might be fixed in any of the upcoming service releases of Rhino 8 or all the efforts are now focused on Rhino 9? I am not aware what the situation with R8 maintenance is.

Have you looked at the suggested topics at the bottom of the page? There are a few comments from the developers.

That one was not suggested to me :smiley: But good finding. That confirms my concerns.