GhPythonlib 'Angle' component changed to the 'Kangaroo' version?

Rhino Rhino for Mac
, , , ,
1

Good morning,

I had occasion to open an older file from January today, and all of my GhPython components are now raising errors. I think I have tracked the error to a change that has occurred in the ghpythonlib.components.angle ? In the past, this angle object was the normal Rhino ‘Angle’ component which takes two vectors, and a plane. This is how a LOT of existing code is written.

Screenshot 2025-06-06 at 9.47.17 AM
Screenshot 2025-06-06 at 9.47.17 AM1116×522 100 KB

But this morning, it now it appears that this angle has changed to be the ‘Kangaroo2’ Angle component, which takes two lines, a rest-angle, and a strength. As a result of this change, lots of code is now erroring.

Screenshot 2025-06-06 at 9.48.18 AM
Screenshot 2025-06-06 at 9.48.18 AM1620×850 213 KB

  1. Is this change intentional? If so, should we expect other changes to the ghpythonlib API? If so, are those changes documented someplace?
  2. How can I access the ‘old’ Angle component through ghpythonlib.components ? I do not want to use the ‘Kangaroo’ version.

Thank you very much,
@ed.p.may

Environment

  • Rhino Version 8 (8.20.25154.13002, 2025-06-03)
  • MacBook Pro
  • Sequoia 15.5 (24F74)
3

@ed.p.may

Hi Ed and thanks for reporting. This is an unwanted side effect of fixing this problem ( RH-85999 Kangaroo component names has changed in NodeInCode). This is definitely not expected and I created the YT below and will push a fix for this soon

RH-87825 NodeInCode Kangaroo.Angle overrides Vector.Angle

4

Hi @eirannejad ,

Ah - I see - np. For the time being, I just swapped in Rhino.Geometry.Vector3d.VectorAngle() which seems to work ok for now.

thanks!
@ed.p.may

1 Like
5

RH-87825 is fixed in Rhino 8 Service Release 21 Release Candidate

1 Like