If a given point p is on the major axis then REllipse::getVectorTo(p) returns one of the major points. In the code this is handled as a special case when the point is in-line (collinear) with the major axis.
This is only correct for points outside the evolute.
On the major axis is defined by getAngle().
This may fail for a magnitude equal to or less than 1e-6.
A point that close to the center should not have a single solution at zero degrees.
The correct solutions are:
- If p is equal to the center ⇒ Two vectors to the two minor points.
- On the major axis and strictly inside the evolute ⇒ Two mirrored vectors.
- On the major axis and on or outside the evolute ⇒ The nearest major point.
- On the minor axis ⇒ The nearest minor point.
An additional problem is now what to return on a duality with full ellipses.
Or for an ellipse arc where both of two results are valid.
getVectorTo() typically returns but one unique result.
For example:
RCircle::getVectorTo(p) returns an invalid vector when the point is near the center.
Then there are an unlimited number of solutions.
Further discovered that the point related to the returned vector may fail x²/a²+y²/b²=1
Although almost on the ellipse within 2.299e-10 … f(x,y) may return 9.5310
This example would fail REllipse::contains while the border is considered as inside.
Meanwhile implemented a 'simple method' to find the nearest point(s) on an ellipse.
Fast converging in 3 steps, no trigs and very accurate, about 24 lines of code.
f(x,y) returns mostly 1.000 with so far:
- a minimum of 0.9999999999999997
- a maximum of 1.0000000000000007.
In other words, it is only off for the last meaningful decimal digit.
With this all methods that are based on REllipse::getVectorTo(p) can be implemented very reliable with tolerance, border flag, … and so on.
By default the normal for a point is given with high accuracy and a tangent is that rotated.
… ..
.
Regards,
CVH
I see a similar behavior from the Drawing Preferences, with respect to Printing - Page.
I didn't start noticing this behavior until I changed my computer to an M4 based Mac Mini running Tahoe. With that change, I started using the ARM based version of QCAD. So, I'm wondering if the problem is ARM based rather than on other operating systems, including Intel based Macs, like my previous one.
]]>
In RCircle::getDistanceTo
getDistanceTo2D is based on getMagnitude2D().
This should be compared with RS.PointTolerance (1e-9), not squared (1e-18).
! ! !
Only true in an arbitrary (unlimited) precision.
The method using the magnitude or the squared magnitude cannot be compared in floating point.
The squared magnitude will hardly ever have a meaningful 18th digit after the comma.
As it is the subtraction of the vector components with no more than 17 significant digits.
A method missing here is RVector::getSquaredMagnitude2D() avoiding + 0.0*0.0 for dz²
Here you use a circular tolerance area in 2D: Less than 1e-9 away in any 2D direction.
Or a spherical tolerance in 3D.
Positions are typically compared using an axis aligned square shape as tolerance range in 2D (RVector::equalsFuzzy2D) or a cubic box in 3D (RVector::equalsFuzzy):
Less than 1e-9 to 1.414214e-9 away in any 2D direction
Or less than 1e-9 to 1.732051e-9 away in 3D.
40 to 70% more tolerant depending 2 or 3D and the direction.
Regards,
CVH
PS:
I can start a comment on GitHub like before but that is no longer accepting inputs.
Claude included major/minor swapping in REllipse::getVectorTo().
This is an existent resource and already used in most cases.
I never encountered a major radius less than the minor but it is plausible.
For a ratio over 1.0, correctMajorMinor() caches the minor point (Line 1205).
Sets a corrected ratio (Line 1206).
And then it sets the major point using REllipse::setMajorPoint() (Line 1207).
setMajorPoint() calls REllipse::correctMajorMinor() again.
This time the ratio is less than 1.0 and nothing is altered.
Because correctMajorMinor() is setting things straight it can simply update
the public attributes: 'ratio', 'majorPoint', 'startParam' and 'endParam' in this order.
correctMajorMinor() is typically called for:
- The valid REllipse constructor.
- When setting the REllipse major point, the ratio
and thus also when setting the minor point.
- When setting the properties of an REllipseEntity.
There is a second analog to REllipse::correctMajorMinor().
The method REllipse::switchMajorMinor() does practically the same but then based on an external test.
In open source only used in RShape::getIntersectionPointsEE (Line 1275 and 1279).
Then called when the major radius is less than the minor radius.
The main difference is that it is skipped when the ratio is less than 1e-9.
fabs(ratio) in line 314 is odd because a negative ratio is invalid … Not rendered.
switchMajorMinor() triggers correctMajorMinor() twice.
It first set the major point equal to the minor point based on the former ratio.
This triggers correctMajorMinor().
Then it sets the reciprocal of the ratio.
This also triggers correctMajorMinor().
switchMajorMinor() can also update the public attributes in direct.
For the record: REllipse::getTangents also swaps major/minor in direct when the point is on the minor axis. This method handles an ellipse as full and doesn't correct end parameters.
Regards,
CVH
Layer is not frozen.
See also:
https://forum.qcad.org/t/manage-viewport-layers-not-persisting-save-and-reopen/11902
Attached screenshots were taken using QT5 and QT6 for comparison (both at 125% scaling). Antialiasing was turned off. Note how the grid dots fade in and out like a moiré pattern.
]]>