Text Objects are great!

Hey!

One of the last couple of updates introduced text support for the speckle viewer, and the rhino translator can now send text objects that display crisp and clear in the speckle viewer! Amazing!!

Noticed some possible improvements on this functionality that might be worth mentioning:

  • text justification not working, defaults to top right in Speckle which can offset text position from the original modell.
  • I could not figure out an easy way to create such text objects in Speckle from Grasshopper. I can think of several workflows that would benefit greatly from being able to send localized 2d/3d text somehow.

Keep up the good work!

I think these text objects are just sent as curves for now, but the plan is to have them become actual text objects sometime soon; this will allow for scaling, justification, better readability etc…
Thanks for the feedback :slight_smile: !

1 Like

Wow. Nice! In that case there must have been a serious upgrade in how speckle handles curves. I remember that before the letters got heavily distorted, (especially the rounded letters being converted to very coarse polylines) which really hurt the readability of the result. These look pretty much perfect now. Looking forward for the next version of this!
Any recomandations on how to get this result from grasshopper?

Hi @Andrei ,

The web team did implement native Text conversion in the viewer back in June, kudos to @alex for the pretty text you are seeing now! He would be able to give you more details on any plans to improve how text justification, scale, etc is handled.

Currently Grasshopper does not support TextEntity objects (which is what we’re sending from Rhino) so our GH connector cannot send text at the moment. It’s likely that we’ll wait until whenever Rhino 8 releases, since that will include expanded GH support on entities like Text, Hatches, and Dimensions, to add Text conversion to our GH connector :sweat_smile:

Thanks for the reply, sounds like a plan!

Hi @Andrei

Thank you for the feedback! :slight_smile:

Indeed, text objects are handled ‘natively’ are not longer made up of curves like they used to be. As of yet, the implementation is still lacking a few features, consistent text justification being just one of them, but we are planning on improving it more in the one of the next iterations

Cheers

2 Likes

I learned something new too! :open_hands::smiling_face_with_three_hearts:

1 Like

@clrkng Ressurecting this thread with an idea:

I was just thinking about this again: We can actually programmatically create rhino TextEntities in GH that in theory would be able to be handled in the same way as in Rhino. Would it be easy to just port this functionality over from the rhino object converter to the grasshopper one for this type of objects?
This would be a temporary fix untill better support is added in Rhino 8, like you mentioned.

image

Hey @Andrei,

I just checked the code and I don’t see anything preventing TextEntities from being converted in Grasshopper, though I haven’t had time to test this yet.

What happens if you pass them through a ConvertToSpeckle node? (if you don’t see that node, go to the top-menu Speckle → Tabs and activate the Dev Components

Hey Alan,

Thanks for checking in so fast. Getting warning text : “1. Cannot convert item {0;1}[0] to Speckle” . Blank output

Yup this also occurred to me, it’s definitely a possible workaround but would require us to implement TextEntity support in GH as per this part of our converter @AlanRynne (I’ll let you decide whether to enable or not, ie if there are other downstream consequences to doing so for a type not natively supported in GH)

Oh i totally missed the CanConvertToSpeckle, it seems like ConvertToSpeckle doesn’t have this condition though :sweat_smile: oopsies

I think we can definitely enable this but we’ll check and get back to you!

Sounds great, I cant wait to test this!