Ladybug Tools text objects not recognized by native Grasshopper "Text Object Info" component

Alakelele · August 6, 2026, 8:19pm

Also, sorry for the spamming, it seems the title output is not recognized by the Text object info

chris · August 12, 2026, 4:29pm

This is because the native Grasshopper “Text Object Info” component uses text objects that were only introduced in Rhino 8. In Ladybug Tools, we use a custom text object class that we built:

github.com/ladybug-tools/ladybug-rhino

ladybug_rhino/text.py

master


      
          class TextGoo(gh.Kernel.Types.GH_GeometricGoo[rh.Display.Text3d],
                        gh.Kernel.IGH_BakeAwareData, gh.Kernel.IGH_PreviewData):
              """A Text object that can be baked and transformed in Grasshopper.
          
              The code for this entire class was taken from David Rutten and Giulio Piacentino's
              script described here:
              https://discourse.mcneel.com/t/creating-text-objects-and-outputting-them-as-normal-rhino-geometry/47834/7
          
              Args:
                  text: A Rhino Text3d object.
              """
          
              def __init__(self, text):
                  """Initialize Bake-able text."""
                  self.m_value = text
          
              @staticmethod
              def DuplicateText3d(original):
                  if original is None:
                      return None

This file has been truncated. show original

… using a sample that Guilio put together on the McNeel forum here:

At some point, I think we will want to move Ladybug Tools over to using the new natively supported text objects that Grasshopper offers in Rhino 8. But doing so would mean that we drop support for Rhino 7 (and Rhino 6 of there’s anyone still using it).

Long story short, I think the earliest we would do this is with the release of Rhino 9. At that point, we will probably make a couple of breaking changes, which will mean that we drop support for Rhino 7 and earlier.

I opened an issue on our GitHub so that we don’t forget to do this in the future:

github.com/ladybug-tools/ladybug-rhino

Eventually swich text module over to using native Rhino/Grasshopper Text Objects

opened 04:29PM - 12 Aug 26 UTC

chriswmackey

enhancement

Grasshopper in Rhino 8 has components to work with text objects. In Ladybug Tool…s, we use a custom text object class that we built: https://github.com/ladybug-tools/ladybug-rhino/blob/master/ladybug_rhino/text.py#L49-L169 ... using a sample that Guilio put together on the McNeel forum here: https://discourse.mcneel.com/t/creating-text-objects-and-outputting-them-as-normal-rhino-geometry/47834 At some point, we will want to move Ladybug Tools over to using the new natively supported text objects that Grasshopper offers. But doing so would mean that we drop support for Rhino 7 (and Rhino 6 of there's anyone still using it). I think the earliest we would do this is with the release of Rhino 9. At that point, we will probably make a couple of breaking changes, which will mean that we drop support for Rhino 7 and earlier. More info is here: https://discourse.ladybug.tools/t/ladybug-tools-text-objects-not-recognized-by-native-grasshopper-text-object-info-component/40676

Alakelele · August 13, 2026, 4:30pm

Oky, thanks for the explanation