Flyspray::

FS#2734: Concerning: Commit 2b1838b

2026-07-27T05:37:26Z

RCircle.getVectorTo was modded to avoid the sqrt() in getMagnitude() and used v.getSquaredMagnitude().
Then comparing that with the square of the default tolerance (1e-18).
Part of Commit d233495

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.

FS#2733: Transparent black or white entities lose transparency with color correction

2026-07-01T09:37:52Z

Color correction strips the alpha channel.

See:
https://forum.qcad.org/t/qcad-shading-of-hatches/11828

FS#2719: Moiré Effect with QT6 on Linux when Display Scaling is > 100%

2026-06-19T10:24:24Z

I have noticed a problem that causes ugly rendering when using the QT6 version of 3.32.7 on KDE/XWayland if my system display scaling is set higher than 100%. The problem does not occur with QT5.

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.

FS#2732: Draw > Hatch > Hatch from Segments…: fails with certain arcs

2026-06-19T10:22:45Z

Choosing one arc fails for example at:

https://forum.qcad.org/t/crosshatch-problems-using-latest-version/11776

FS#2731: Crash with invalid image of size 0

2026-06-15T11:29:07Z

An image with size 0/0 can cause a crash when trying to render the image.

FS#2730: Misc > Reset Configuration: Exception when using dialog button flags

2026-06-15T09:07:25Z

Andrew,

The exception is skipped silently and the configuration is not reset.

Nowadays standard dialog buttons or flags are created using the makeQMessageBoxStandardButtons library function.

new QMessageBox.StandardButtons(…) seems functional too.

.setStandardButtons(A | B) and .setDefaultButton(B) is seen as another method.

Regards,
CVH

FS#2729: File > Bitmap Export: margin creates offset

2026-06-12T15:03:47Z

The margin in the bitmap export dialog causes an offset, not a margin all around cutting off part of the drawing.

FS#2728: AutoSave: creates backup files with wrong extension

2026-06-11T13:46:48Z

AutoSave may create backup files with wrong extensions or overwrite files with wrong extensions when loading non-DXF files (SVG, PDF, etc.)

FS#2727: Text Dialog: white space other than regular space not preserved

2026-06-01T11:42:25Z

Alternative white space such as "Thin Space", U+2009 should be preserved as such. While rendered correctly as thin space with TrueType fonts, the thin space is converted to a regular space when the text is edited.

FS#2726: Edit > Drawing Pref > Printing > Page: Page size not recognized for page sizes with decimals [Qt6]

2026-05-19T12:33:02Z

Page sizes that are not whole Millimeters are not recognized when set (e.g. Arch D).