You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Hello, I am using the library to enumerate closed polylines, free floating lines and multileaders in a dwg file. Multileaders are attached to the corners of polylines and to the start or end point of lines. One multileader can be attached to only one entity (polyline or line). I can get X/Y coords of all polylines, lines and multileaders. My aim is to know which multileader is connected to which entity (polyline or line) by comparing X/Y coords of corners (polyline) or start/end point (line) with X/Y of multileaders.
In the dwg file (attached), there is a line which has one attached multileader to its start/end point. But when I enumerate all the entities and output their X/Y coords, there is no match between multileader X/Y coord and line start/end point. The values are different. For getting multileader X/Y coord I am using the property ContextData.BasePoint.X/Y.
Then there is a polygon which has another multileader attached to its corner and their (the corner and multileader) coords match to the pixel. Could you check it please.
To Reproduce
usingACadSharp.Entities;usingACadSharp.IO;usingACadSharp;CadDocumentdoc=DwgReader.Read(@"test.dwg");foreach(Entityitemindoc.Entities){if(itemis not null&&itemisLwPolylinepolyline){Console.WriteLine("Polyline");foreach(LwPolyline.Vertexvertexinpolyline.Vertices){Console.WriteLine($"\tX = {vertex.Location.X}, Y = {vertex.Location.Y}");}}elseif(itemis not null&&itemisLineline){Console.WriteLine("Line");Console.WriteLine($"\tstart X = {line.StartPoint.X}, start Y = {line.StartPoint.Y}, end X = {line.EndPoint.X}, end Y = {line.EndPoint.Y}");}elseif(itemis not null&&itemisMultiLeadermultiLeader){Console.WriteLine("multiLeader");Console.WriteLine($"\tX = {multiLeader.ContextData.BasePoint.X}, Y = {multiLeader.ContextData.BasePoint.Y}, Text = {multiLeader.ContextData.TextLabel}");}}Console.ReadLine();
Expected behavior
Coords of mltileaders attached to start/end point or corners of polygon should have correct coords (same as the corresponding corner or start/end point).
Screenshots
This is an output of the code snippet above. The mutlileader with text vnitrni cara is attached to the Line yet their coords do not match.
Here is a screenshot of the dwg with circled multileader attached to an end point of the line.
Describe the bug
Hello, I am using the library to enumerate closed polylines, free floating lines and multileaders in a dwg file. Multileaders are attached to the corners of polylines and to the start or end point of lines. One multileader can be attached to only one entity (polyline or line). I can get X/Y coords of all polylines, lines and multileaders. My aim is to know which multileader is connected to which entity (polyline or line) by comparing X/Y coords of corners (polyline) or start/end point (line) with X/Y of multileaders.
In the dwg file (attached), there is a line which has one attached multileader to its start/end point. But when I enumerate all the entities and output their X/Y coords, there is no match between multileader X/Y coord and line start/end point. The values are different. For getting multileader X/Y coord I am using the property
ContextData.BasePoint.X/Y
.Then there is a polygon which has another multileader attached to its corner and their (the corner and multileader) coords match to the pixel. Could you check it please.
To Reproduce
Expected behavior
Coords of mltileaders attached to start/end point or corners of polygon should have correct coords (same as the corresponding corner or start/end point).
Screenshots
This is an output of the code snippet above. The mutlileader with text
vnitrni cara
is attached to theLine
yet their coords do not match.Here is a screenshot of the dwg with circled multileader attached to an end point of the line.
Additional context
test.zip
The text was updated successfully, but these errors were encountered: