Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Grasshopper_Toolkit: allow a two-way resolution for Geometry display #366

Open
epignatelli opened this issue May 21, 2019 · 1 comment
Open
Assignees
Labels
priority:standard type:feature New capability or enhancement

Comments

@epignatelli
Copy link
Member

Following BHoM/BHoM_Engine#960 (comment), and the recent formalisation of physical and analytical objects.

The idea is to have two levels of resolution for Geometry display: physical and analytical.
e.g. when displaying a Bar we can either render the actual meshed cross section, or we can render the analytical centerline of the bar. We should allow both.

Three ways:

  • Having a component that can be dropped on the canvas, that switches between one viz to another with a toggle
  • Having an additional dropdown in the Grasshopper menu that allows us to switch between them
  • Adding an option to the right click menu of each component. This would be done at the component level rather than the overall solution level
@epignatelli epignatelli added priority:standard type:feature New capability or enhancement labels May 21, 2019
@epignatelli epignatelli self-assigned this May 21, 2019
@epignatelli epignatelli added this to the BHoM 2.4 β MVP milestone Jul 15, 2019
@epignatelli epignatelli removed this from the BHoM 2.4 β MVP milestone Aug 19, 2019
@adecler
Copy link
Member

adecler commented Sep 25, 2019

We need to keep in mind Dynamo when considering our options

@adecler adecler changed the title Grasshopper_Toolikit: allow a two-way resolution for Geometry display Grasshopper_Toolkit: allow a two-way resolution for Geometry display Apr 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority:standard type:feature New capability or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants