Grasshopper

algorithmic modeling for Rhino

This is less of a bug but an inconsistency in terms/component display.

When using many of the intersection tools, the component will turn red if it fails to find any intersections on ANY tree. That is, even if it finds some intersections, if any planes fail to find an intersection, the whole component turns red. As someone who tries to avoid red components on the canvas, this seems like a behavior that could be improved. It seems like if, for instance, a plane and surface fail to intersect, it should result in a something less extreme than a red component which usually in GH notes a serious error. 

The actual results of the output seem correct (empty branches), but it seems like that is all that is needed. No red component needed since the empty branches already note that no intersections were made on those branches. I would suggest the component remains gray or if absolutely needed, turns orange as a warning that some intersections failed. Red components should be preserved for only serious errors like entering the wrong data types, etc.

Views: 273

Replies to This Discussion

Agreed. It should always be possible to fix red components, which is clearly not the case here.

Great! Thanks! I hate telling my students to ignore red components when things like this happen. 

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service