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

CurtainPanel.ByElement unreliable #2302

Open
andydandy74 opened this issue Mar 30, 2015 · 6 comments
Open

CurtainPanel.ByElement unreliable #2302

andydandy74 opened this issue Mar 30, 2015 · 6 comments

Comments

@andydandy74
Copy link

As shown in the screenshot below, CurtanPanel.ByElement returns null as soon as a curtain wall contains door or window elements (which, in my experience, is typically the case). Nested wall elements or curtain walls luckily pose no problem.
cwp_limitations
As a first step, it would be great to not have the node fail to deliver those elements that are not doors or windows if such elements are present.
As a second step, it would be even better if doors or windows could also be returned. It makes a lot more sense to have a full inventory of all elements in a curtain wall/system.
Also, in 0.7.5 walls and curtain walls are actually being returned as belonging to the Walls category, not as Curtain Panels. That wasn't such a bad thing because it allows for easy filtering of the results...

@andydandy74
Copy link
Author

@pboyer
Copy link
Contributor

pboyer commented Mar 30, 2015

@kronz

On Mon, Mar 30, 2015, 5:18 AM Andreas Dieckmann notifications@github.com
wrote:

Example files posted here:

https://github.com/CAAD-RWTH/ClockworkForDynamo/tree/master/issues/4128_CurtainPanel.ByElements%20unreliable


Reply to this email directly or view it on GitHub
https://github.com/DynamoDS/Dynamo/issues/4128#issuecomment-87606668.

@kronz
Copy link

kronz commented Mar 31, 2015

Tracking internally as http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-6859

@andydandy74
Copy link
Author

In case anyone else runs into this problem while this bug is still active: I needed this urgently so I went ahead and made this as a custom node.
Available as Element.Panels in package Clockwork.

@andydandy74
Copy link
Author

Another small addition:
When we use wall elements as curtain panels, Revit actually seems to store two elements: a curtain panel placeholder and the actual wall element that appears in the panel schedule. When we collect curtain panels in Dynamo by category we will, however, receive the placeholder element – which means we do not get those elements that will actually appear in a panel schedule.
This can be remedied by querying panels for their host panels with the FindHostPanel() method. This method will return the actual wall element (the placeholder elements are quite useless). For normal CW panels it should return null if memory serves correctly.
For more information on how this currently impedes workflows refer to this discussion: http://dynamobim.com/forums/topic/host-issuequestion/

@ParametricMonkey
Copy link

Still an issue some 9 years later...#3043

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

No branches or pull requests

4 participants