FilledRegion.GetBoundaries() API bug?

AlbertoRosario — Tue, 16 Jul 2019 01:18:51 GMT

For Revit 2016 through 2018.

Shouldn't frDayZone.GetBoundaries() have the same "Count" quantity as boundaryprofile?

Here's the problem code:Note "Count=0" for iCurveLoopTwo So, creating a Solid fails with line written like:

Solid fSolid = GeometryCreationUtilities.CreateExtrusionGeometry(frDayZOne.GetBoundaries(), XYZ.BasisZ, 100000);

Obviously because of an unforeseen problem with the .GetBoundaries() FilledRegion method returning a "Count" of zero.

When attempting to create said Solid with an empty IList<Curveloop> gives error message:

"Input array of CurveLoops is empty. Parameter name: profileLoops"

Yet, frDayZone.GetBoundaries() returns the expected "Count" successfully creates a Solid and executes all the command code, JUST on the FIRST run oddly enough, right after a System.Forms.OpenDialog box is used to load a tag into the document.This only works first time loading the Tag via System.Windows.Forms.OpenFileDialogIf the command is run again the error with FilledRegion.GetBoundaries() "Count = 0" will occur.

Also, if the command has never been run and the tag already exists in the document, the error occurs.

To repeat, the main question is:

Why is rDayZone.GetBoundaries() returning "Count = 0" instead of"Count=1" like boundaryprofile?

Re: FilledRegion.GetBoundaries() API bug?

AlbertoRosario — Tue, 16 Jul 2019 16:59:13 GMT

Figured this out already.

Just needed to wrap this in another "Transaction" and now it works as expected.

Hope this helps others that may get thrown off for a moment like I did.

topic Re: FilledRegion.GetBoundaries() API bug? in Revit API Forum

FilledRegion.GetBoundaries() API bug?

Re: FilledRegion.GetBoundaries() API bug?