Flyspray:: https://www.qcad.ch/bugtracker/ Flyspray::QCAD Bugtracker: Recently edited tasks 2026-06-19T10:24:24Z FS#2719: Moiré Effect with QT6 on Linux when Display Scaling is > 100% https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2719 2026-06-19T10:24:24Z Alex Holden 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. 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2732 2026-06-19T10:22:45Z Andrew Choosing one arc fails for example at: https://forum.qcad.org/t/crosshatch-problems-using-latest-version/11776 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2731 2026-06-15T11:29:07Z Andrew An image with size 0/0 can cause a crash when trying to render the image. 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2730 2026-06-15T09:07:25Z CVH 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 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2729 2026-06-12T15:03:47Z Andrew The margin in the bitmap export dialog causes an offset, not a margin all around cutting off part of the drawing. 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2728 2026-06-11T13:46:48Z Andrew AutoSave may create backup files with wrong extensions or overwrite files with wrong extensions when loading non-DXF files (SVG, PDF, etc.) 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 https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2727 2026-06-01T11:42:25Z Andrew 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. 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] https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2726 2026-05-19T12:33:02Z Andrew Page sizes that are not whole Millimeters are not recognized when set (e.g. Arch D). See also:https://forum.qcad.org/t/qcad-will-not-save-paper-size/11680/4 Page sizes that are not whole Millimeters are not recognized when set (e.g. Arch D).

See also:
https://forum.qcad.org/t/qcad-will-not-save-paper-size/11680/4

]]> FS#2725: View > Property Editor: block name property shown without choices https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2725 2026-05-18T10:15:45Z Patrick Junker 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 regardsPatrick 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 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 :-)

]]> FS#2724: QCAD/CAM QT6 Freeze during CAM EXPORT. https://www.qcad.ch/bugtracker/index.php?do=details&task_id=2724 2026-05-12T21:23:19Z Mário Carvalho Versions QT6 3.32.8.0, 3.32.9.0 on WIN10 and LINUX Ubuntu 25.10 (don’t work in WIN7) Versions QT5 OK on WIN7, WIN10 and LINUX My PlanetCNCW64 software accepts G41/42 but gave an error on generated g-code G40 (“Arc without IJK or R is not valid” G40 X85.6 Y62.24 Their bug?). So, I had to fill “Interpolate axes with line segments” in CAM Configuration. A little window QCAD CAM “Regenerating tool path…” opens, shows 50% all the time, and a button “Abort” that closes that window when clicked, but doesn’t stop the process; a lot of messages “regenerating tool paths…” run at the bottom with great speed, as expected. With QT6 but not QT5, after a while, these messages start slowing more and more, when I believe the arc segments are being generated, but keep a normal speed on lines, till the program freezes. During this process, with both QT6 and QT5, the memory used is growing, but is not released until the program is closed. Garbage collection problem? Versions QT6 3.32.8.0, 3.32.9.0 on WIN10 and LINUX Ubuntu 25.10 (don’t work in WIN7)

Versions QT5 OK on WIN7, WIN10 and LINUX

My PlanetCNCW64 software accepts G41/42 but gave an error on generated g-code G40 (“Arc without IJK or R is not valid” G40 X85.6 Y62.24 Their bug?). So, I had to fill “Interpolate axes with line segments” in CAM Configuration. A little window QCAD CAM “Regenerating tool path…” opens, shows 50% all the time, and a button “Abort” that closes that window when clicked, but doesn’t stop the process; a lot of messages “regenerating tool paths…” run at the bottom with great speed, as expected.

With QT6 but not QT5, after a while, these messages start slowing more and more, when I believe the arc segments are being generated, but keep a normal speed on lines, till the program freezes. During this process, with both QT6 and QT5, the memory used is growing, but is not released until the program is closed. Garbage collection problem?

]]>