Version 2.0.9-44. Create a circle using "Center, Radius" and snap to the center of a cross that was created, enter .270 as the radius, measure center to "12 o'clock" is .2697, measure center to "3 o'clock" is .270, measure center to 6 o'clock is .2703, measure center to 9 o'clock is .270.
Can you please attach a DFX file containing this issue.
dxf attached. toggle layer 0 on/off to see the dimensions that I have an
issue with
Last edit: ravas 2016-03-11
DXF for review. Toggle layer 0 on/off to see the dims that I am referring to.
Last edit: Steve S 2016-03-11
This is a matter of snapping or exactness. The circles center is not identical with the intersection point of the horizontal and vertical line. See the attached image. Select the circle, then the center is shown as a green dot and then zoom in to the center.
Move the circle to the intersection point or use center snapping and disable intersection snapping to draw the correct dimension.
Note that it wasn't from creating the .270R circle at the intersection. I
created a 1.00R circle then changed the radius via the properties command
to .270. The horizontal dims were OK, but the vertical dims were the ones
that were off.
Last edit: ravas 2016-03-11
Note that I originally created a 1.00R circle at the intersection and checked out OK. I then changed the radius of said circle via the properties dialogue. The horizontal dims were OK, but the vertical dims were off by .0003
Can you re-create that?
Yes, I've reproduced the behaviour with your DXF file.
Look at my screen shot. The gap in Y direction, between the green dot, which represents the center of the 0.270 radius circle, and the red crossed circle, which marks the end of the dimension line, is 0.0003.
Thats why the dimension at 6 o'clock is 0.2703 and at 12 o'clock 0.2697.
There is a gap in X direction too, but much smaller, smaller as the dimensions precision.
Using only the center and middle snap mode gives correct results for me, as the dimensions snap to the center of the circle. But with intersection snap mode on, the dimensions snap to the line intersection, what results in the discribed issue.
Now I've understood the underlying problem. I'll create a new bug ticket as this is unrelated to dimensions and misleading.