Flyspray::

FS#2734: Concerning: Commit 2b1838b

CVH — Wed, 22 Jul 2026 04:59:47 +0000

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)

In RCircle::getDistanceTo
getDistanceTo2D is based on getMagnitude() and should be compared with RS.PointTolerance (1e-9)

Here you use a circular tolerance area in 2D: Less than 1e-9 away in any XY direction.

Positions are typically compared using an axis aligned square shape as tolerance range in 2D or a cubic box in 3D:
RVector::equalsFuzzy2D or RVector::equalsFuzzy or less than 1e-9 to 1.414214e-9 (to 1.732051e-9) away in any direction.
40 to 70% more tolerant depending the direction.

Only true in an arbitrary (unlimited) precision.
In floating point these methods can not be compared.
The squared magnitude will hardly ever have a meaningful 18th digit after the comma.

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

Andrew — Wed, 01 Jul 2026 09:37:31 +0000

Color correction strips the alpha channel.

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

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

Andrew — Fri, 19 Jun 2026 08:20:46 +0000

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

Andrew — Mon, 15 Jun 2026 11:25:31 +0000

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

CVH — Sat, 13 Jun 2026 06:22:03 +0000

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

Andrew — Fri, 12 Jun 2026 15:03:17 +0000

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

Andrew — Thu, 11 Jun 2026 13:46:40 +0000

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

Andrew — Mon, 01 Jun 2026 11:40:27 +0000

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]

Andrew — Tue, 19 May 2026 12:32:26 +0000

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

FS#2725: View > Property Editor: block name property shown without choices

Patrick Junker — Fri, 15 May 2026 22:42:07 +0000

Hi,

I remember that in earlier versions of QCAD the field type of Referenced Block: in the Property Editor used to be a dropdown list, which used to be populated with all blocks. The selected referenced block was of course the selected item in this list. With this dropdown list it used to extremely easy and efficient to swap out a block in the drawing by simply picking another block from the list. I'm sure this dropdown list was still present in QCAD version 3.25.2.

In newer versions of QCAD - at least since release 3.32.3 - the field type of Referenced Block: in the Property Editor has changed to a simple text input field. To swap out a block in a drawing one does now have to know the exact name of a block and type that name correctly into the field. If the name of a non existing block is entered, the entire field is cleared and the original block is removed from the drawing as well.

For me this is clearly appears like a bug, maybe introduced with an update of the QT library?

Would be great if the old, logical and efficient behaviour could be restored!

Thanks and best regards
Patrick

BTW, I'm using macOS Sequoia (15), which is missing from the OS picker in the QCAD Bugtracker. Also, the dropdown has two entries for Mojave (10.14), where one of them should likely be High Sierra (10.13), which is missing, too