Originally Posted by
Ed Jobe
I made some changes. Use the collection's Add method to add more than one item.
Whoops, my fault I knew that just didn't type it correctly, sorry.
Originally Posted by
Ed Jobe
Depending on what you are doing with the points afterward, you might consider making objects from the points, rather than using variants. For example, using a Type or Class.
The scope of pl_lst is entirely in one routine as of now. What type of object(s) would you suggest vs variants? Variants work now, but when I convert to .NET down the road, I know variants are not allowed.
Current implementation of pl_lst:
This loop creates construction lines and determines the intersection of these lines vs an existing construction line. Once all the intersection points are captured, I will later back fill with real lines, dimensions and polylines.
Code:
.
.
.
Do While st < t1
s1 = MakePoint(st, 0#, 0#)
Set oXLine2 = oAcadDoc.ModelSpace.AddXline(s1, MakePoint(s1(0), s1(1) + 12#, s1(2))) 'AddXLine places points in World CS
oXLine2.TransformBy oAcadDoc.ActiveUCS.GetUCSMatrix 'Transform back to UCS
oXLine2.Color = acYellow
oXLine2.Update
s1a = cAcadTransCoords.TransCoordsFromWorldToUCS(oAcadDoc, oXLine2.IntersectWith(oXLine, acExtendNone)) 'Intersect Point is World, trans to UCS
pl_sublist(0) = s1: pl_sublist(1) = s1a
pl_lst.Add pl_sublist
st = IIf(ctr = 0, st + dKerf, st + dMatlWidth)
ctr = Abs(ctr - 1)
Loop
.
.
.