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)

IDCategoryTask TypeSeveritySummary  descStatusProgress
864QCAD (main)Bug ReportLowTemplate Preview/Info doesn't shows the sheet orientati...Assigned
Task Description

“Create New Drawing from Template” Browser can’t readout the Page orientation ...

 1785 QCAD (main)Bug ReportLow Template / Viewport scale issue Closed
Task Description

Given: Template with prepared Paper Space Frame/Titleblock scale = 1:1.
Drawing 1:1
First Viewport / scale 1:1 / inserted in Paper Space = everything fine,
Second Viewport / scale 0.02 will scale the Paper respective to the new Viewport scale but the Frame/Titleblock isn’t scaled.

 1313 QCAD (main)Bug ReportLow Task not implemented Closed
Task Description

it’s not true !!!!!!

My request it’s not implemented !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 715 QCAD (main)Bug ReportLow Tangent Warning Messages are wrong ... Closed
Task Description

I like to draw a line tangent between two circle.

I choose the line/tangent tool - click the first circle - get a Warning Message: “No tangent possible” confirm the Message with the OK Button.
Choose the second circle - get again a Warning Message: “No tangent possible” confirm also this Message with the OK Button.

Result: A line tangent between two circle ......

 291 QCAD (main)Bug ReportLow Tangent Point - Circle Closed
Task Description


 247 QCAD (main)Feature RequestLow tab names sometimes shortened too much Closed
Task Description

When many tabs are open, the name of contained drawing is not fully shown. One way that some mdi applications do, is to append the name of the active tab to the top window title, which is also useful in other ways. At least a tool tip with the full name of the file on the tab top was nice.

1233QCAD (main)Feature RequestLowTab key to cycle between selected objectsAssigned
Task Description

I think it’s a useful adition and makes it easy to select objects that are overlapped. I know there is a selection filter, but sometimes this is faster and/or all the objects share the same type and such things.

If I remember correctly, Inkscape has this behaviour.


 1816 QCAD/CAMBug ReportLow TAB function in CAM module fails  Closed
Task Description

When using (adding a TAB on a radius fails).


When length of the TAB is set to 1 mm.

After export to *.nc code the code is not ok.

And then check this is NC viewer or gcode sender the length is not set to 1 mm but is smaller.

On a line this function (TAB) is correct working.

1445QCAD (main)Bug ReportLowSwitching off grid scaling can break rulersAssigned
Task Description

See also:

 1610 QCAD/CAMPerformance IssueLow Switching from one drawing to another slow Closed
Task Description

When switching from one drawing to another, the 3D view is updated which can be slow, especially for drawings with many text entities.

See also:

 111 QCAD (main)Feature RequestLow Switch for line width display Closed
Task Description

Switch on / off line width display (display mode between normal and draft)

 191 QCAD (main)Bug ReportLow SVG PG export text vertical and horizontal alignment Closed
Task Description

QCAD offers horizontal and vertical alignment choices for text. This is not carried over to PG exported SVGs. Currently QCAD sets the “dy” attribute on text nodes in a way, such that any text in SVG will look like the QCAD vertical alignment was set to “Top” and the horizontal one to “Left”.

Naively one can just omit the “dy” attribute and in SVG this will look like the QCAD vertical alignment was set to “bottom”. At least for single line texts that should be good.

The horizontal alignments can be recreated in SVG with the “text-anchor” attribute for text nodes. The values “start”, “middle” and “end” correspond to the QCAD “left”, “center” and “right” choices.

 192 QCAD (main)Bug ReportLow SVG PG export stroke width should not scale Closed
Task Description

When PG exporting to SVG, stroke-widths are scaled with the drawing, while they should not.

 730 QCAD (main)Bug ReportLow Svg PG export splines broken Closed
Task Description

With the 3.0.3 point release (latest available for Linux systems), SVG PG exporter fails to export splines:

Uncaught exception at /opt/qcad-3.0.3-prof-linux-x86/scripts/ImportExport/SvgExporter/SvgExporterPG.js:72: TypeError: Result of expression ‘splineSeg.getDegree’ [undefined] is not a function.
72 var degree = splineSeg.getDegree();

The objects returned from getBezierSegments() do not provide the methods of RSpline.

 194 QCAD (main)Bug ReportLow SVG PG export scale text Closed
Task Description

Text scaling in PG SVG exporter is missing just two small additions: These attributes are not taken care of by now:

font-size, dy

Just use the current value times scale: eg 2.5 * 0.1 to have a scale of 1:10. Looks good here.

 195 QCAD (main)Bug ReportLow SVG PG export scale points Closed
Task Description

Points are not scaled when PG exported to SVG:

Points as crosses are created eg. like this:

d=m 2.5,3 1,0 M 3,2.5 l 0,1

and in SVG look fine like that (scale 1/10):

d=m 2.95,3 0.1,0 M 3,2.95 3,3.05

stroke-width should be left unchanged.

 193 QCAD (main)Bug ReportLow SVG PG export scale hatches Closed
Task Description

The SVG PG exporter does not scale hatches.

 315 QCAD (main)Feature RequestLow SVG PG export polylines Closed
Task Description

Polylines may consist of lines and arcs. The SVG PG exporter writes them as all straight lines. A better mapping than polyline then was path, as is done with arcs now.

 204 QCAD (main)Bug ReportLow SVG PG export font styles Closed
Task Description

Patch to PG export font styles “bold” and “italic” to SVG. (This only works when a file with the right style is loaded into QCAD, as QCAD will yank such style information upon saving.)

 202 QCAD (main)Bug ReportLow SVG PG export font colors Closed
Task Description

White text gets exported as white text, while it should be exported as black text. Just like it is with lines. Attached patch makes text rendering use the conversion function that is already in the code base.

 198 QCAD (main)Bug ReportLow SVG PG export dimensions Closed
Task Description

SVG PG exporter, scaled or unscaled, currently only exports the labels of dimensions. Missing are

ticks, arrows, and lines of the dimension.

It will not be as simple as inkscape does it, wrap it all in a <def>.

 190 QCAD (main)Bug ReportLow SVG PG export dimension labels alignment Closed
Task Description

Dimension labels in QCAD are (always?) centered on the dimension line, while in exported SVGs the text starts from the center and extends into the writing direction. This can trivially be fixed by adding the attribute “text-anchor:middle” to the respective SVG “text” nodes.

 122 QCAD (main)Bug ReportLow SVG of hatch with "hole" Closed
Task Description

A hatch my have “holes”, if it eg. is made of two forms, an inner form, and and outer form, where the outer form is filled while the inner form appears like a window inside of the fill, that lets the background be seen.

QCAD exports such hatches as two SVG paths in one single entity. But the “hole” is lost in the process. I know of two workarounds, that preserve the original intention of the QCAD drawing, both get the same result most of the time, the second one looking more robust and easier to implement:

# draw the outer form clockwise, draw the inner form counterclockwise
# set the “fill-rule:evenodd” attribute on the fill definition of the entity

Drawing a star like in the SVG spec in QCAD actually produces the same picture – so that should be the way to go.


 967 QCAD (main)Bug ReportLow SVG import: SVG transformations can lead to wrong arc d ...Closed
Task Description

importing a svg generated by inkscape from a downloaded eps results in all contained arcs drawn in wrong direction

 1096 QCAD (main)Feature RequestLow SVG import: support scale transforms Closed
1 Task Description

Add support for scale transforms in SVG import.

Original report:

When importing an SVG created with Inkscape, one of the elements (rectangle) is shifted (mirrored?) to the left.
The example (back.svg) is appended. If you open it with Inkscape, you see the rectangle should be above the “USB” label.

My impression is that the sign of the X coordinate is swapped for some reason. At least if I mirror it
using two points on the Y axis, it seems to appear where it should be.

Apart from this, also the dimensions are wrong after import. In the original SVG, the outer shape is 144.3mm wide.
This is also visible in the header of the SVG:


However, after importing to QCad, the width is measured as 40.7247. This is a puzzling factor of 3.5433 which doesn’t look
like metric/imperial conversion issue but like a complete misinterpretation of the sizes/units used in the SVG.

 1244 QCAD (main)Feature RequestLow SVG import: consider original unit Closed
Task Description

Add support for importing units other than defaults (pixels) based on unit given in svg:width / svg:height attributes.

 1201 QCAD (main)Feature RequestLow SVG import: add support for circles, ellipses Closed
1 Task Description

The attached file should result in two overlapping circles, it does not, it results in a single ellipse.

The “<circle ... />” directive seems just be ignored in this case, but in other instances I have seen it result in ellipses.

And the “<ellipse ... />” directive should of course result in a circle, when rx and ry are the same.

 1175 QCAD (main)Bug ReportLow SVG import turns polylines into polygons Closed
Task Description

(I’m running on FreeBSD, but that was not an option in the selection for Operating System)

When importing a SVG file in version 3.7.5, it qcad turns polylines into polygons.

I’m attaching a trivial .SVG file showing this, it should *not* render as a rectangle,
but as a “rectangular upper case C”.

And many thanks for making good quality CAD software available to the FOSS community.

 603 QCAD (main)Bug ReportLow SVG import straight path segments Closed
Task Description

I noticed, that paths are not fully imported into QCAD. I rewrote case “m” of “SvgImporter” like below, that way also straight line segments are drawn correctly. Case “M” should be similar:

      case 'm':
          x = ox = coords[0];
          y = oy = coords[1];
          x0 = x;
          y0 = y;
          for (k=2; k<coords.length; k+=2) {
              x += coords[k+0];
              y += coords[k+1];
              this.importLine(ox, oy, x, y);
              ox = x;
              oy = y;
1242QCAD (main)Bug ReportLowSVG import DPI box should use localized decimal separat...Assigned
Task Description

I wanted to make it so, that SVG units translate 1:1 into CAD units; I use the German localized QCAD and entered 25,4 into the box with the wrong result, i.e. the same as 25; Entering 25.4 got me what I wanted: The question box needs the point and ignores the comma. Would be nice if it could use the localized separator.

 96 QCAD (main)Feature RequestLow SVG Import Closed
Task Description

Complete SvgImporter.js and SvgImport.js

  1. Implement SvgImporter.prototype.importFile to import the SVG file with the given fileName. Reading only all path data without any attributes or transformations is fine as a first step. SvgImporter.prototype.importFile() currently imports one hard coded path data as proof of concept.
  2. Implement SvgImport.prototype.beginEvent() to show a file open dialog that lets the user choose an SVG file to import.
  3. Support SVG as file format for part library items through SvgImporter

This should be enough to import any SVG file in library/symbols

 818 QCAD (main)Bug ReportLow SVG Exporter crashes on polyline Closed
Task Description

Attached sample drawing, that kills QCAD 3.1 beta when exporting to SVG.

The crash happens in line 38 of SvgExporterPG in function SvgExporterPG.prototype.exportPolyline

var pp = new RPainterPath(polyline.toPainterPath());
208QCAD (main)Feature RequestLowSVG export: support custom line weightsAssigned
Task Description

Find way to support custom line weights for SVG export. See also forum thread: http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1594

 916 QCAD (main)Feature RequestLow SVG export: make zero line width behaviour configurable Closed
Task Description

Somewhere in the 3.1 series the SVG exporter (both precise and PG) started to make lines that are zero (0) width in CAD 0.01 (@scale 1:1) points wide in exported files (0.1 @scale 1:10). I use such lines to constrain exported files to a common size and rather not have them show. In my view, this is a regression, as there is no reason for changing line weight, isnt it? If I wanted the lines to have weight, I’d draw them with a weight.

 1842 QCAD (main)Bug ReportLow svg export shows texts in different place Closed
Task Description


when I export a dxf draw to svg the text objects shows in a bit different place.

QCAD version is

 137 QCAD (main)RefactoringLow SVG Export precision Closed
Task Description

In files exported with the (even PG) exporter I sometimes see values like these: 334.99999999999994 or 570.0000000000001 and very often 12 digits of precision.

To safe on file size, I suggest, that QCAD rounds values on SVG export to eg. three places. When viewed in an ordinary web browser, that will result in a precision of 1 inch / 96dpi / 1000 = 0.00026mm, not? Ends should still meet.

 334 QCAD (main)Bug ReportMedium SVG Export Polygons, arcs converted to straight lines. Closed
Task Description

When exporting a drawing to SVG, polygons containing arcs (trimmed circles in this case) are converted to straight lines. If the polygon is exploded first, then it exports correctly. Of course, this isn’t useful if closed polygons are required for the program using the SVG file. Solid hatch fills export correctly. See attached DXF and corresponding SVG export.

 217 QCAD (main)Bug ReportLow SVG export ignores exportPoints setting Closed
Task Description

Both SvgExporters ignore the exportPoints setting. Attached patch takes care of that. To be applied from within the “scripts” directory.

Nitpicking in File/SvgExport/SvgExport.js, var properties is meant to be a plain Object instead of an Array, isn’t it?

 90 QCAD (main)Bug ReportLow SVG Export group nesting Closed
Task Description

The SvgExporter opens a “group” for some entities, but never closes that group. The resulting nesting can get quite deep and does not conform to the original. I tentatively patched the script as below:

--- SvgExporter.js-orig	2011-05-23 10:55:17.239998578 +0200
+++ SvgExporter.js	2011-05-23 10:55:17.239998578 +0200
@@ -226,6 +226,11 @@
 //        RFileExporterAdapter.prototype.exportEntity.call(this, this.realEntity
 //                .data(), false);
 //    }
+    // dimensions and block references are grouped, close the group tag here
+    if (isDimension(entity) || isBlockReferenceEntity(entity)) {
+        this.writeEndElement();
+    }
 SvgExporter.prototype.endEntity = function() {

There might be a better way, but that is what I came up with on short notice.

 58 QCAD (main)Bug ReportLow SVG Export file name suggestion Closed
Task Description

Quick SVG Export suggests file name “Untitled 1 [*].svg”

Remove [*] (comes from window title).

 138 QCAD (main)RefactoringLow SVG Export entity properties "By Layer" and "By Block" Closed
Task Description

If I understand correctly, SVG export uses svg groups to keep QCAD block entities. This in itself is very useful. There is no way to correctly keep layer information, as QCAD blocks can contain elements on different layers, while SVG only knows about groups. That is a deficiency of SVG.

To save on file size, there was some potential to get rid of ever repeating same attributes on entities, eg: style=”stroke:#000000;stroke-width:0.25;stroke-dasharray:2.16,1.08”

To optimize “By Block” is easy: just set the attribute on the SVG group, and omit on below entities styled “By Block”.

To optimize “By Layer” is a little more involved, but might be solved by using css:
- Create a class by the name of the Layer
- add the class attribute to elements styled “By Layer”

Then only individually styled entities would get a style attribute, and filesize of SVG could be halved in most cases.

This just an idea :) Having written this, I now realize, that QCAD can style weight, pattern, color each extra, so the optimazition could only be applied to entities, where everything is “By Layer” or “By Block”. But that should be the case most of the time.

 324 ECMAScriptFeature RequestLow SVG export depends on GUI Closed
Task Description

SvgExporter.js uses PrintPreview to parse the scale string, and therefore depends on the qt GUI part. That should not make maintenance harder to call RMath directly there? Results seem to match from a first look.

--- SvgExporter.js~	2011-10-20 14:11:45.527589416 +0200
+++ SvgExporter.js	2011-10-20 14:12:46.277502814 +0200
@@ -1,6 +1,5 @@
  * File exporter implementation for the SVG format.
@@ -116,7 +115,7 @@
     this.svgUnitAbbr = ret[1];
     // scale
-    this.scale = Print.parseScale(this.scaleStr);
+    this.scale = RMath.parseScale(this.scaleStr);
     var bb = this.doc.getBoundingBox();
     var size = bb.getSize();
 79 QCAD (main)Bug ReportLow SUSE binary crashes under Fedora Closed
Task Description
  • during the start up
  • last info from splash screen: LibraryBrowser: Directory: metric
./qcad: line 5:  2321 Segmentation fault      (core dumped)
LD_LIBRARY_PATH=/home/martin/opt/qcad-3.0.0-tp1-prof-linux /home/martin/opt/qcad-3.0.0-tp1-prof-linux/qcad-bin $*
(gdb) bt
#0  0x03180194 in __strncmp_ssse3 () from /lib/libc.so.6
#1  0x08c7741e in __xmlParserInputBufferCreateFilename ()
#2  0x04333e04 in xmlParserInputBufferCreateFilename ()
   from /usr/lib/libxml2.so.2
#3  0x043bc9c0 in xmlNewTextReaderFilename () from /usr/lib/libxml2.so.2
#4  0x041fde98 in ?? () from /usr/lib/libgnomevfs-2.so.0
#5  0x041fe381 in gnome_vfs_mime_get_value () from /usr/lib/libgnomevfs-2.so.0
#6  0x041fbb38 in gnome_vfs_mime_get_icon () from /usr/lib/libgnomevfs-2.so.0
#7  0x040d0ab6 in gnome_icon_lookup () from /usr/lib/libgnomeui-2.so.0
#8  0x040d1037 in gnome_icon_lookup_sync () from /usr/lib/libgnomeui-2.so.0
#9  0x0240ee92 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#10 0x026a0658 in QFileIconProvider::icon(QFileInfo const&) const ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#11 0x025cd467 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#12 0x025c2f89 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#13 0x025c3ba4 in QFileSystemModel::index(QString const&, int) const ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#14 0x025c7289 in QFileSystemModel::sort(int, Qt::SortOrder) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#15 0x025bc86c in ?? ()
---Type <return> to continue, or q <return> to quit---
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#16 0x025c6d68 in QFileSystemModel::qt_metacall(QMetaObject::Call, int, void**)
    () from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#17 0x08881dc2 in RFileSystemModel::qt_metacall(QMetaObject::Call, int, void**)
#18 0x02cd3c83 in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#19 0x02cdede6 in QMetaCallEvent::placeMetaCall(QObject*) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#20 0x02ce09a0 in QObject::event(QEvent*) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#21 0x025c07c3 in QFileSystemModel::event(QEvent*) ()
598QCAD (main)Feature RequestLowSupport tangents between ellipsesAssigned
1 Task Description

To add support for drawing tangents between ellipses.

See topic:

 507 QCAD (main)Bug ReportLow Support reversed planes for all entities (currently onl ...Closed
Task Description

See RDwgEllipseImporter::import

 1094 QCAD (main)Feature RequestLow Support OS X 10.9.x (Maverick) Full Screen Pattern Closed
Task Description

It would be nice if the OS X Pro version could support the standard OS X full screen pattern in the same way as native OS X applications.

With this I mean that applications in full screen will create a temporary new desktop as long as they are in full screen mode.

1098QCAD (main)Feature RequestLowSupport for set of layersAssigned
Task Description

Many constructions refer to a basis of elements, which stay constant in all follow-ups. As an example there is a floorplan and I would like to create different variations of room layout (e.g. A and B). In my example the basis consists of 30 layers an each variation needs 10 further ones. At last there are 50 different layers in my drawing. Designing layout A needs layer 1 to 30 (basis) and 31 to 40 (A) to be shown, but 41 to 50 (B) must be invisible. Now I modify Var.B which makes me to single click the visibility of 31 to 40 (A) to be not shown and 41 to 50 (B) to be shown. You’ve got it?

It would be great help, to save the set of all shown layers by an individual name in a pulldown-menu. Visibility of my variations could be chosen by userdefined “set of layers”, e.g. “Var-A”, “Var-B” and “Var-A_but_different”. In this way I pick just one set-name in my pulldown-list instead of marking and demarking between countless layers.

In my opinion this tool would be a small aspect in QCad but a giant leap for user-pleasentness ;-)

693QCAD (main)Feature RequestMediumSupport for external references (XREF)Likely to be implemented
14 Task Description

Support for external references (XREF)

 264 QCAD (main)Feature RequestMedium Support for "Layouts" (paper space, viewport) Closed
25 Task Description

There is one important ACAD feature that I would really like to see supported in QCAD3 and that is “Layouts”

Looking at the block lists, it seems to me that it can’t be too much extra work to support it, since the model space and different paper spaces are already shown there - and one can edit it.

QCAD draws infinitely easier than ACAD and drawing layouts is a primary feature of ACAD. With this in QCAD I can hardly see why anyone that does 2D work would need ACAD at all.

 297 QCAD (main)Feature RequestLow Support drawing linetype scale factor (LTSCALE) Closed
Task Description

Support drawing linetype scale factor (LTSCALE)

Showing tasks 201 - 250 of 1848 Page 5 of 37<<First - 3 - 4 - 5 - 6 - 7 - Last >>

Available keyboard shortcuts


Task Details

Task Editing