QCAD Bugtracker

QCAD - 2D CAD System.

Click here for a documentation of the DokuWiki formatting syntax that can be used in reports

Please search for existing tasks (also closed ones) before opening a new task.

Please make sure that you are using the latest Version of QCAD before posting a bug (menu Help > Check for Updates)

IDCategory  descTask TypeSeveritySummaryStatusProgress
1743QCAD (main)Bug ReportVery LowDraw > Text: Wrong bounding box for text with empty sup...Assigned
1 Task Description


I have a drawing where I use text with superscript. In this case when I use autozoom, it does not work as I expect. It includes the 0,0 coordinates too. The problem also occures when I export the drawing into svg.

I attached an example, just use the autozoom.


1760QCAD (main)Bug ReportVery LowSelf-crossing polylines can't be cut twice at segment c...Assigned
Task Description

Re-entering dividing problem from  FS#1757 

Divide the poly selecting near segment 1 at the segment crossing.
> A new node is inserted on the crossing and made start and end node.
Divide the poly again selecting near segment 2 at the segment crossing.
> no division appears to be done.

One can’t divide the second segment at the crossing

Presumed intended behaviour like  FS#1750 


1762QCAD (main)Bug ReportVery LowModify // .... selection of entities on locked layer al...Assigned
Task Description

Not served with the degration to ‘Suggestion’ FS#1759.
Demanded closing FS#1759 & re-entered

Locking entities (by layer) to avoid selection,eg. nearby,very close by or on the same spot, does not have the intended influence.

Asumed wrong:
- Modify DI
- Modify B2
- Modify D3
- Modify MT
These 4 need a single entity to be selected and selection of a locked entity is allowed.(=questionable)
The action will allways leed to ‘not allowed’.(=correct)

- Modify RM
- Modify CH
- Modify RN
These 3 need a pair of entities.
RM: Selection of a locked limiting entity is allowed (=questionable), enity to trim not.(=correct)
The action will trim unlocked entities to the locked limiter.(=questionable)
CH & RN: Selection of a pair of entities is allowed.(=questionable)
Trimming if ‘trim’ is on will not occur because locked and leeds to ‘not allowed’.(=correct)
The creation of the bevel or rounding on an active locked layer will not occur because locked and leeds to ‘not allowed’.(=correct)
The creation, except for polyline segments (because locked themself), on an active unlocked layer will be done.(=correct)

Less severe but still questionable: (because these don’t necerally act on the locked entities themselves)
- Modify OF
- Modify OH
- Modify SS
OF: Selection of a locked base entity is allowed.(=questionable)
The preview is casted only if the active layer is unlocked.(=correct)
The creation is only done on an active unlocked layer.(=correct)
OH: Selection of a locked base entity is allowed.(=questionable)
Selection of point references from entities on locked layers is allowed.(=questionable)
The preview is casted only if the active layer is unlocked.(=correct)
The creation is only done on an active unlocked layer.(=correct)
SS: Selection of point references from entities on locked layers is allowed.(=questionable)
Strechting is only done for unlocked entities. (=correct)

1765QCAD (main)Bug ReportVery LowErrors with polyline offsetAssigned
1 Task Description

Win 7 32 bit QCAD 3.20.1

Ofsset of a base-line with arcs results in massive ammount of errors.
Most of them occur as a cluster of very tiny segments and are part of the offset. (zoom far in at the red circles)
Mostly they occur where the offsetted arcs should merely be trimmend pairwise.
Some occur as detached entities or as detached strings of entities very near the offset (strings not documented).
Spooks occur at opposite site when base-line is not closed.
360° curls can occur with R = Offset.
Null-entities may occur (not documented, hard to find and not able to copy).

The base-line is checked and sound and has mixed tangentially or not tangentially connected arcs.
Offsetting the mother base-line of the base in the file has similar effect but not all and/or different ones.
Also encountered with offseting polys from fonts.
Used to define pocket paths for CNC.
Detected because the CNC driver will not accept Self-crossers, Null-entities or open ends depending on the settings.

Work arround is to explode and select small entities but this does not solves the issues.
1) Choosing the tolerance large enough will detect small segments that should stay.
2) Recombining will generate new ones at the place where the main segments remain crossed.
Cleaning up the paths is a daunting process with some thousand segments for several offsets.

I assume this has an infuence on the CAM part of QCAD too unless the offset method is different.

1506dxflibFeature RequestLowwriteVPort parametersAssigned
Task Description

Add parameters to the function DL_Dxf::writeVPort.
This way users will be able to specify the desired viewport.

Is the github the official repository? Are pull requests sent there accepted?

976dxflibBug ReportLowDXF import errors related to hatches, textsAssigned
Task Description


1180dxflibBug ReportLowdxflib cannot open files with international characters ...Assigned
3 Task Description

With dxflib, QCAD cannot open any file with Chinese file name or path name, it popups a “Important Error” dialog.
But the writing (”Save As” command) with Chinese file name or path name is of no problem.
Does it mean dxflib can only handle single byte characters file name/path name?
WinXP, QCAD 3.8.0

1203dxflibBug ReportLowImages not saved (dxflib)Assigned
Task Description

I am doing a bit of landscaping and using a (big) ortophoto as one of my layers in order to sanity-check on the ground measurements.

The layer contains a point and the image and nothing else.

The image is a 8MB file: “PNG image data, 4200 x 2980, 8-bit/color RGB, non-interlaced” and it is scaled to 210 coordinate units (meter) horizontally in the drawing.

With approx 50% probability the image disappears during Save, as see for instance in this diff of the DXF file:

      @@ -158699,28 +153057,6 @@ AcDbXrecord
      -  5
      - 90
      -  1
      - 10
      - 20
      - 11
      - 21
      -  0

The point in the same layer does not similarly disappear, the bug only seems to affect images.

I have seen this bug from version to git as of yesterday (63e06c778926a803bdfbffdf27b8c24d41511072).

I have not been able to correlate the bug with anything.

Looking closer at the DXF file (attached), there seems to be some residuce of attempts to insert images in protected/invisible layers, so this may be some kind of refcounting issue.

(Any chance of getting FreeBSD into the “Operating System” field ?)

1542dwg2svgFeature RequestLowdwg2svg: add switch to show only given layer(s)Assigned
Task Description

Implement a command line switch to only show a list of given layers for dwg2* command line tools.

1021dwg2pdfFeature RequestLowdwg2pdf: switch to set block to exportAssigned
1 Task Description

Add a command line switch to dwg2pdf to export a given block instead of “*Model_Space”.

1700dwg2pdfFeature RequestLowdwg2pdf: output multiple layoutsAssigned
Task Description

Add support to specify multiple blocks (layouts) to output (one per page).

Showing tasks 351 - 361 of 361 Page 8 of 8<<First - 4 - 5 - 6 - 7 - 8

Available keyboard shortcuts


Task Details

Task Editing