-
Notifications
You must be signed in to change notification settings - Fork 635
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
DYN-6840: add new boundary condition node #15270
Conversation
Still have to add resources (although I am not sure if we want more localization for 3.2) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-6840
UI Smoke TestsTest: success. 2 passed, 0 failed. |
namespace GeometryUIWpf | ||
{ | ||
[IsVisibleInDynamoLibrary(true)] | ||
[NodeName("PanelSurfaceBoundaryConditions")] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we just make this singular like the enum itself - PanelSurfaceBoundaryCondition
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PanelSurfaceBoundaryCondition will collide with the ENum coming from ProtoGeom (at least in the library view)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aparajit-pratap is the layout spec good enough for now ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move the other PanelSurfaceBoundaryCondition
node under this new BoundaryCondition
category as well? I think more than one node can have the same name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
or maybe there's a special setting to allow same name nodes under the same parent ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or I can change the name of the new node (again)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe only the same named nodes are allowed if and only if they have different inputs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Amoursol what do you think about the layout above ? 2 entries with the same name "PanelSurfaceBoundaryCOndition"
ONe is a dropdown node, the other is category (I think) for individual boundaryCOndition nodes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pinzart90 As it's still experimental, I don't think layoutspec changes matter too much. So we can do any of those changes and evaluate later if need be.
On the name front, could we please name it "Select Boundary Condition"? This is similar to some Revit paradigms. Do we also need to mark it an Action, not a Query?
Probably not plural - unlike image. Sorry on that miss!
[OutPortTypes(nameof(PanelSurfaceBoundaryCondition))] | ||
[OutPortDescriptions("PanelSurface BoundaryCondition enum value")] | ||
[IsDesignScriptCompatible] | ||
public class PanelSurfaceBoundaryConditionDropDown : DSDropDownBase |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there is an enum based dropdown...
https://github.com/DynamoDS/DynamoRevit/blob/bcb122017c2e5ebe63e4198f8b8f84a3abc5305a/src/Libraries/RevitNodesUI/GenericClasses.cs#L128
maybe it makes sense to move that class here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is also an EnumBase class inside Dynamo, but it generates the string values not the actual enum types.
public abstract class EnumBase<T> : DSDropDownBase |
I guess they could all be made into a more generic class. I would consolidate them in another task
/// </summary> | ||
public override IEnumerable<AssociativeNode> BuildOutputAst(List<AssociativeNode> inputAstNodes) | ||
{ | ||
//Some of the legacy categories which were not working before will now be out of index. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this comment mean?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nothing, I can remove it
@@ -164,7 +164,7 @@ public void ProducesCorrectOutputFromCoreDirectory_preloadedbinaries() | |||
FromDirectoryCommand.HandleDocumentationFromDirectory(opts); | |||
|
|||
var generatedFileNames = tempDirectory.GetFiles().Select(x => x.Name); | |||
Assert.AreEqual(707, generatedFileNames.Count()); | |||
Assert.AreEqual(705, generatedFileNames.Count()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just changed this to 709??
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll pull your changes and update this
Purpose
https://jira.autodesk.com/browse/DYN-6840
Add new boundary condition node for panel surfaces
Declarations
Check these if you believe they are true
*.resx
filesRelease Notes
Add new boundary condition dropdown node for panel surfaces.
Reviewers
(FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR)
(FILL ME IN, optional) Any additional notes to reviewers or testers.
FYIs
(FILL ME IN, Optional) Names of anyone else you wish to be notified of