# Rhino 8 Feature: GH1 Is Now More Than Just Geometry!

**URL:** <https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294>\
**Category:** Serengeti (Rhino BETA)\
**Tags:** rhino8\
**Created:** [September 1, 2022, 8:07pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294 "2022-09-01T20:07:40Z")\
**Posts on this page:** 20\
**Page:** 7

<div class="post-metadata">

**Author:** ![Intuos](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/intuos/32/771015_2.png) [@Intuos](https://discourse.mcneel.com/u/Intuos)\
**Post date:** [August 14, 2023, 9:21am UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/124 "2023-08-14T09:21:29Z")

</div>

As far as attributes are concerned, it seems like I can only query attribute keys with the ‘Field expression’ component paired with the ‘Evaluate text fields’ component (see top)

 ![afbeelding](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/c/7/b/c7bed52fdf561f6a2e9a7a5355f4afd3fc0c9e27.png)

If I do the same with the Elefront component ‘Get User Value’ (see bottom), you can see it takes no additional computation time. I really do hope a faster native attribute workflow will be considered or is already in the works.

---

<div class="post-metadata">

**Author:** ![AndyPayne](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andypayne/32/611612_2.png) [@AndyPayne](https://discourse.mcneel.com/u/AndyPayne)\
**Post date:** [August 14, 2023, 3:43pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/125 "2023-08-14T15:43:45Z")

</div>

If you’re looking to extract the User Text keys or values from geometry, then I would recommend using the User Text component (Rhino → Content). Simply connect the object which contains some user text to the Content input and then the output will contain the keys and values of that object. If the value contains a formula (ie. expression) then you could use the Evaluate Text Fields component to parse the formula and return the numeric value.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/a/f/2/af21011b23a06c0eced845606f28709349e5c4ec.png)

---

<div class="post-metadata">

**Author:** ![Intuos](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/intuos/32/771015_2.png) [@Intuos](https://discourse.mcneel.com/u/Intuos)\
**Post date:** [August 16, 2023, 7:07am UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/126 "2023-08-16T07:07:19Z")

</div>

I actually forgot about this component, for multiple attributes, it gets the job done with one more component than Elefront.

 ![afbeelding](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/2/1/921e483171bb9f63b528edf3fa33fa1daef58680.png)

---

<div class="post-metadata">

**Author:** ![michaelvollrath](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/michaelvollrath/32/479405_2.png) [@michaelvollrath](https://discourse.mcneel.com/u/michaelvollrath)\
**Post date:** [August 16, 2023, 12:49pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/127 "2023-08-16T12:49:30Z")

</div>

That’s handy. I never honestly tried that component 😄

---

<div class="post-metadata">

**Author:** ![Ryan14](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/ryan14/32/498212_2.png) [@Ryan14](https://discourse.mcneel.com/u/Ryan14)\
**Post date:** [August 16, 2023, 1:22pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/128 "2023-08-16T13:22:04Z")

</div>

> [@guido](#):
>
> > [@AndyPayne](#):
> >
> > clipping planes? named sheet views?
> 
> Please! Please!  
> GH components for Layout & Detail management could open so many possibilities 🥳  
> Documentation in Rhino is still so painful.  
> I have always hoped @rajaa would develop section tools for Gh. Managing hatched sections on named sheets via grasshopper would be unbelievable!

I put my Please! Please! In for this to. This would be the most amazing thing ever!

---

<div class="post-metadata">

**Author:** ![AndyPayne](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andypayne/32/611612_2.png) [@AndyPayne](https://discourse.mcneel.com/u/AndyPayne)\
**Post date:** [August 16, 2023, 3:17pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/129 "2023-08-16T15:17:29Z")

</div>

Ah. Ok. I guess I didn’t understand that you were trying to get a specific user key/value. Your solution is completely valid (and fairly concise). We did add some additional components for filtering/grouping data based on a user text key, but that solution is likely the same amount of components as what you showed in your example. Still, you might find [this post](https://discourse.mcneel.com/t/grouping-sorting-and-filtering/162619) useful for future reference.

---

<div class="post-metadata">

**Author:** ![Czaja](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/czaja/32/472252_2.png) [@Czaja](https://discourse.mcneel.com/u/Czaja)\
**Post date:** [August 16, 2023, 4:05pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/130 "2023-08-16T16:05:41Z")

</div>

Every WIP update I’m checking if Leaders can be modified. After a few months, I need to ask: should they work already? I’m kinda excited about Grasshopper annotation possibilities.

_Leader is not outputting curve, can’t modify existing Leader only bake a new one_

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/2/c/c/2cc4c28b5ff328bdd6c214f089c58ba881042158.png)

---

<div class="post-metadata">

**Author:** ![AndyPayne](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andypayne/32/611612_2.png) [@AndyPayne](https://discourse.mcneel.com/u/AndyPayne)\
**Post date:** [August 16, 2023, 4:40pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/131 "2023-08-16T16:40:31Z")

</div>

What happens if you use the new “Explode Objects” component. This was recently added and should work on leaders, dimensions, text, blocks, curves, breps, meshes, etc… It should return the same results as the “Explode” command in Rhino. Does this give you the curves you’re looking for?

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/8/0/1/8015e415ff3885e98fd7ca5b7a74bd32303d54bb.png)

---

<div class="post-metadata">

**Author:** ![Czaja](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/czaja/32/472252_2.png) [@Czaja](https://discourse.mcneel.com/u/Czaja)\
**Post date:** [August 16, 2023, 4:51pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/132 "2023-08-16T16:51:37Z")

</div>

I only get geometries if I reference the leader from the query, not when I directly point to the leader.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/d/c/d/dcdf60721ae0256cad475eedab07d53e332dd84e.png)

---

<div class="post-metadata">

**Author:** ![michaelvollrath](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/michaelvollrath/32/479405_2.png) [@michaelvollrath](https://discourse.mcneel.com/u/michaelvollrath)\
**Post date:** [August 16, 2023, 4:56pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/133 "2023-08-16T16:56:22Z")

</div>

@Czaja I believe this is because you have no leader feeding into the leader component.

To be able to get the items from it you need to have a leader feeding into the Leader input, otherwise it will return empty values.

@AndyPayne Right Click “Set One Leader” works on my end, doesn’t mean that’s the case for them.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/5/a/95ae200918320145587c908a147ed7aa2670850f.png)

---

<div class="post-metadata">

**Author:** ![AndyPayne](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andypayne/32/611612_2.png) [@AndyPayne](https://discourse.mcneel.com/u/AndyPayne)\
**Post date:** [August 16, 2023, 4:57pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/134 "2023-08-16T16:57:39Z")

</div>

Actually, I think @Czaja is correct. There may be a bug here. I believe he’s right-clicked on the Leader input and selected “Set One Leader” and referenced the leader that way. I’m checking on this.

---

<div class="post-metadata">

**Author:** ![Czaja](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/czaja/32/472252_2.png) [@Czaja](https://discourse.mcneel.com/u/Czaja)\
**Post date:** [August 16, 2023, 7:52pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/135 "2023-08-16T19:52:41Z")

</div>

Yes, that’s what I did. I can extract parameter out of the Leader input but surprisingly Leader primitive component cant be found in the top bar or found using search.

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/2/e/4/2e420fbc69a2acf43bed7cd6511f61689fd88610.png)

---

<div class="post-metadata">

**Author:** ![AndyPayne](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/andypayne/32/611612_2.png) [@AndyPayne](https://discourse.mcneel.com/u/AndyPayne)\
**Post date:** [August 16, 2023, 8:13pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/136 "2023-08-16T20:13:27Z")

</div>

Yes. That’s correct. We have hidden some of the new data type parameters only because there are so many of them. We may revisit that idea in the future… and as you pointed out, you can always get to them by using the “Extract Parameter” button.

---

<div class="post-metadata">

**Author:** ![guido](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/guido/32/761602_2.png) [@guido](https://discourse.mcneel.com/u/guido)\
**Post date:** [August 16, 2023, 8:43pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/137 "2023-08-16T20:43:18Z")

</div>

> [@AndyPayne](#):
>
> We have hidden some of the new data type parameters only because there are so many of them. We may revisit that idea in the future…

Haha, maybe you will need a “show really obscure components” tick-box in preferences 😅

---

<div class="post-metadata">

**Author:** ![Japhy](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/japhy/32/487647_2.png) [@Japhy](https://discourse.mcneel.com/u/Japhy)\
**Post date:** [August 22, 2023, 2:51pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/138 "2023-08-22T14:51:39Z")

</div>

Split this topic on August 22, 2023, 2:51pm UTC

7 posts were split to a new topic: [Add a modifier + click combination to add a panel to a specific output](https://discourse.mcneel.com/t/add-a-modifier-click-combination-to-add-a-panel-to-a-specific-output/164429)

---

<div class="post-metadata">

**Author:** ![Intuos](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/intuos/32/771015_2.png) [@Intuos](https://discourse.mcneel.com/u/Intuos)\
**Post date:** [August 25, 2023, 12:33pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/139 "2023-08-25T12:33:02Z")

</div>

Is it possible to scale the radial dimension based on the active viewport extents?

I don’t see a way to know which viewport is active. In this case, I have two top views, because I do all my work inside a single viewport. The viewport may even change to 3D later, so using name as input is bound to break.

I am working on a live curve fillet, for which I want to see the fillet dimensions in the viewport. Considering this is an urban layout, I have to zoom in quite a lot to see the dimensions, whereas larger dimensions would obscure the view when zoomed in. These are just for modeling aids that need to be scaled relative to have a fixed size regardless of the zoom level.

[https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/2/2/e/22ef44fe8e9fcdfde5c94aee781cd4ad65eb9396.mp4](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/2/2/e/22ef44fe8e9fcdfde5c94aee781cd4ad65eb9396.mp4)

What would currently be the recommended method for doing this?

---

<div class="post-metadata">

**Author:** ![michaelvollrath](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/michaelvollrath/32/479405_2.png) [@michaelvollrath](https://discourse.mcneel.com/u/michaelvollrath)\
**Post date:** [August 25, 2023, 1:28pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/140 "2023-08-25T13:28:33Z")

</div>

@Intuos probably there is a system exposed parameter that does this but in case not here’s a (probably stupid) possible solution:

Scaling the Text Size by Camera Distance:

 ![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/5/4/c/54c1e5ae08cb85370991e572af6e3a67c2537df6.png)

```auto
import rhinoscriptsyntax as rs

# Get the camera location of the perspective view
camera_location = rs.ViewCamera()

# Calculate the distance between the camera and the object
distance = rs.Distance(camera_location, CP)

# Output the distance
TextSize = round(distance *.01,3)

ghenv.Component.Message = "Distance: " + str(distance) + "\nText Size: " + str(TextSize)

```

This is just an example and production wise would be a baking/performance nightmare.

I need to hunt for the actual method that could write dynamic text size automatically.

Then we just would apply that method to the output of the dimension component I believe.

Dynamically overriding this property I believe would do the trick.

![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/a/2/9/a2996a027dc37da6fa2faacdf562e1687f4d593c.png)

I think the python could respond to an event handler and when the camera changes or mouse zooms the model space scale could change accordingly.

A really silly way would be to ignore the camera position all together and just increment the mouse scroll wheel or exploit the zoom function. zoom out + text size, zoom in -text size

[![image](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/a/f/b/afba7c266c67c8efd43efa9011b881159805a3f8.jpeg)](https://michaelvollrath-my.sharepoint.com/personal/michael_toyblock_co/_layouts/15/stream.aspx?id=%2Fpersonal%2Fmichael%5Ftoyblock%5Fco%2FDocuments%2FTOYBLOCK%2FPROJECTS%2FPROJECT%5FENDGAME%2FEXTERNAL%20SHARING%2Fdynamic%5Ftext%5Fscaling%5Fexample%2Emp4&ga=1)

---

<div class="post-metadata">

**Author:** ![Intuos](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/intuos/32/771015_2.png) [@Intuos](https://discourse.mcneel.com/u/Intuos)\
**Post date:** [August 25, 2023, 2:20pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/141 "2023-08-25T14:20:09Z")

</div>

Actually, I could just grab the first viewport and use the Y extents to set a value:

 ![afbeelding](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/3/8/938e8b1f96b4e3c36add72db00b787c85f27c460.png)

It’s rather rough but gets the job done. Expression isn’t all that correct, but I don’t have time to improve it now before posting.

[https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/f/2/9f20e519ae7f81dd72cca312d17c9894cd5765f0.mp4](https://global.discourse-cdn.com/mcneel/uploads/default/original/4X/9/f/2/9f20e519ae7f81dd72cca312d17c9894cd5765f0.mp4)

---

<div class="post-metadata">

**Author:** ![michaelvollrath](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/michaelvollrath/32/479405_2.png) [@michaelvollrath](https://discourse.mcneel.com/u/michaelvollrath)\
**Post date:** [August 25, 2023, 2:23pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/142 "2023-08-25T14:23:36Z")

</div>

Nice I forgot about the View nodes in R8!

---

<div class="post-metadata">

**Author:** ![Intuos](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/intuos/32/771015_2.png) [@Intuos](https://discourse.mcneel.com/u/Intuos)\
**Post date:** [August 25, 2023, 2:45pm UTC](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294/143 "2023-08-25T14:45:02Z")

</div>

It wasn’t immediately obvious to me that the component also worked on orthographic views. 😅  
Overall, I am really impressed by the radial dimension + viewport component. 👍👏

[Previous page](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294.md?page=6)

[Next page](https://discourse.mcneel.com/t/rhino-8-feature-gh1-is-now-more-than-just-geometry/147294.md?page=8)