Python challenge for G1 Wip

[Piotr]

Since Human is not loading in WiP, I am looking for Text to Screen replacement.

Open AI wasn’t very successful in creating the solution, but Grok got it from the first attempt. After ca. 30 exchanges we got pretty close to the solution with some limitations.

I wanted to replicate the number and order of the inputs, but it failed to flush the text from the Rhino screen, so the boolean needed to be added.

GROK - TXT 2 SCREEN.gh (8.2 KB)

Leaving input as True and close Grasshopper makes the text still appear on the screen.

Can anyone, with deeper understanding of the issue have a look at it? The goal is to have the B input gone and the displayed text disappearing when the Grasshopper session is closed.

[AndersDeleuran]

That Grok code is quite convoluted! I’d recommend having a look at this content. It demonstrates a general approach to drawing things in GhPython using the SDK mode (i.e. that one can use to build all sorts of heads-up-displays):

GHPython Content From AECtech+ Barcelona Workshop

Hi All, I ran a short GHPython workshop at the AECtech+ event in Barcelona. I used this GitHub repository for sharing files with the workshop participants, and thought I’d share all the content here as well. Here is the workshop and content descriptions/links from the GitHub readme file: Dynamically Drawing and Reacting to Things with GHPython There is more to running GHPython components in SDK Mode than compiling plugins. We will demonstrate, explore, and combine these overlooked features th…

Also, here’s a basic example of drawing into screen space:

Draw To Screen Space Foreground From DrawViewportWires

For posterity, I did a bit more testing and cobbled together what appears to resolve this. Basically, getting rid of the hack to pipe into DrawViewportWires and instead run a conditional statement in DrawForeground that checks if the component preview is on, that we are in the correct Grasshopper document (basically the same as Giulios original solution, doh!), and in the active Rhino view: [2023-09-27 10_12_08-Rhino 7 Commercial - Perspective] 230927_ScreenLegendDebug_00.gh (8.0 KB) Edit: …

Note that I use DrawOverlay now to avoid gamma issues in rendered viewports

Edit: Here’s a quick go in Rhino 9 WIP with your inputs:

260112_Text2Screen_GHPython_Deleuran_00.gh (5.3 KB)

[Piotr]

Hi Anders

I new Grok’s solution isn’t elegant at all (as it was loading for a quite a while), but, at least, I had something to start with.

Your solution is great, with one question on my side:

Why it is not working with point defined by text panel?

(but there is always bypass to this problem )

Anyway, many thanks! ***** (5 stars) solution.

PS: hot to get rid of the OLD marker?

[AndersDeleuran]

@Piotr

Why it is not working with point defined by text panel?

You can set the Point type hint explicitly to perform the cast (also, I forgot to hook up the Font code):

@Piotr

PS: hot to get rid of the OLD marker?

You can turn this setting off:

As I’ve commented in several topics, IMO GhPython has been prematurely marked as old/obsolete. This is another case where the newer IronPython component does not appear to have feature parity (i.e. can do the same thing as GhPython can ):

260113_Text2Screen_GHPython_Deleuran_00.gh (10.7 KB)

Edit: @eirannejad might know how to subscribe to drawing events with the new scripting components.