-
Notifications
You must be signed in to change notification settings - Fork 188
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
Comments
On Mon, Mar 30, 2015, 5:18 AM Andreas Dieckmann notifications@github.com
|
Tracking internally as http://adsk-oss.myjetbrains.com/youtrack/issue/MAGN-6859 |
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. |
Another small addition: |
Still an issue some 9 years later...#3043 |
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.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...
The text was updated successfully, but these errors were encountered: