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

Wish: "Select Divided Surface Families" sorting in 0.7 #2194

Open
ColinDayOrg opened this issue Oct 12, 2018 · 4 comments
Open

Wish: "Select Divided Surface Families" sorting in 0.7 #2194

ColinDayOrg opened this issue Oct 12, 2018 · 4 comments

Comments

@ColinDayOrg
Copy link
Contributor

Issue by IanSiegelKPF
Tuesday Jul 08, 2014 at 16:58 GMT
Originally opened as DynamoDS/Dynamo#1897


Would absolutely love if the list output of "Select Divided Surface Families" node was structured as a list of lists, just like it was in 0.6.3. In 0.7 it returns a single flattened list of every family instance.

Thanks!

@ColinDayOrg
Copy link
Contributor Author

Comment by MarkThorley
Thursday Jul 10, 2014 at 15:09 GMT


Can you not just build a sublist from the flattened list you get?

@ColinDayOrg
Copy link
Contributor Author

Comment by IanSiegelKPF
Thursday Jul 10, 2014 at 17:36 GMT


Yes, but the way 0.6.3 automatically sorted the families by U and V made the workflow incredibly easy to organize point data for non-rectangular surfaces. It's an especially helpful feature for architects and designers without a strong computational background, and would also minimize the amount of customization required to adapt the component to different geometry/applications.

@ColinDayOrg
Copy link
Contributor Author

Comment by andydandy74
Saturday Dec 13, 2014 at 19:08 GMT


I am just noticing this now. Please bring back the nested list structure!

@ColinDayOrg
Copy link
Contributor Author

Comment by andydandy74
Saturday Dec 13, 2014 at 19:25 GMT


Just noticed another way to approach this: Select the divided surface using Select Model Element and then use DividedSurface.UDivisions (or alternatively VDivisions) to get the information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant