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 TypeSeveritySummaryStatusProgress  desc
288QCAD (main)Performance IssueLowopening dwg file takes very long [improved]Assigned
Task Description

Opening a 4 MB dwg file results in no-response for about five minutes. Opening the same file with DraftSight takes less than five seconds.

137QCAD (main)RefactoringLowSVG Export precisionAssigned
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.

1056QCAD (main)RefactoringVery LowDead and wrong code in RSPlatform.cppAssigned
Task Description

I am considering pushing the following diff:

--- a/src/core/RSPlatform.cpp
+++ b/src/core/RSPlatform.cpp
@@ -205,25 +205,6 @@ int RS::getCpuCores() {
     cores = sysinfo.dwNumberOfProcessors;
 #elif defined(Q_OS_UNIX)
     cores = sysconf( _SC_NPROCESSORS_ONLN );
-#elif defined (Q_OS_MAC) || defined (Q_OS_BSD4) || [...]
-    nt mib[4];
-    size_t len;
-    /* set the mib for hw.ncpu */
-    mib[0] = CTL_HW;
-    mib[1] = HW_AVAILCPU; // alternatively, try HW_NCPU;
-    /* get the number of CPUs from the system */
-    sysctl(mib, 2, &cores, &len, NULL, 0);
-    if (cores < 1) {
-        mib[1] = HW_NCPU;
-        sysctl( mib, 2, &cores, &len, NULL, 0 );
-    }
-#elif defined(Q_OS_HPUX)
-    cores = mpctl(MPC_GETNUMSPUS, NULL, NULL);
-#elif defined(Q_OS_IRIX)
-    cores = sysconf( _SC_NPROC_ONLN );

(truncated list to manage size)

I see that most of this was put in there as a kind of a note-to-self originally, however _SC_NPROCESSORS_ONLN is implemented by every realistically possible targets anyway, so for all practical purposes, this is dead weight.

A couple of questions remain, though:

  • #ifdef Q_OS_WIN32 should probably be Q_OS_WIN, so as to include win64 as well.
  • Assuming the real purpose for this function is to determine how many parts a particular task is to be split into in the future, if and when QCAD gets the need to split expensive tasks among multiple CPUS, “core” probably shouldn’t be static - CPUs are hot-pluggable today, and while one probably doesn’t do that on a laptop, it’s not unfeasible in, say, a VDI environment.


1323QCAD (main)SuggestionLowImprove command line support in QCADAssigned
Task Description


As a typical command line draftsman (still using acad10 for dos, since microsoft doesn’t supoort Win NT anymore),
I noticed a severe lack on command line acces in QCAD.

For example I find the icon and pixel selecting methods within qcad very confusing and rude.

With the normal cad Select command I can select exactly what en how I want it.

I intend not to be rude, but I find my drawing screen littered all over with all kind of very specialist menu’s,
tools and options. Sorry, I just want to make a drawing at the natural intuitive way, as with a pencil.
So I use command line Commands, such as Move, Copy, Change, Select, a.s.o.
For a ‘Command scripting’ user (-batching is a different tool!-),
it seems to me logical these basic commands should be accessable.

1324QCAD/CAMSuggestionVery LowConfusing Copy / Move optionAssigned
Task Description


Using the Copy and Move command the [ ] Use current layer and attributes’ is confusing.

Perhaps [ ] change copy /moved set to current layers and attributes. is more suitable.

1375QCAD (main)SuggestionVery LowInstall in hidden folderAssigned
Task Description

After each update, I add a dot before the ~user/opt folder (and in the program launcher) created by QCAD to unclutter my file manager’s appearance. Would be easy, I think, to make the installer put the program directly in ~user/.opt, and nobody would miss that folder while browsing through daily used files.

And what about installing the program as root, so all users of a computer could use it without personal installs, and only personal setting files created by users would be kept in ~user/.opt/qcam.


1678QCAD (main)SuggestionLowProperty Editor dialogAssigned
Task Description

The line for “General properties”, “Layer” the line is too narrow,
so you do not see the layer name when the Property Editor is pinned to the side.
(see Forum - Suggestions and Feedback):

1740QCAD (main)SuggestionLowMake unprintable layers also hidden in print previewAssigned
Task Description

Make unprintable layers also hidden in print preview

1754QCAD (main)SuggestionLowWhen Selecting multiple blocks that contain the same at...Assigned
Task Description

When selecting multiple blocks that contain the same attribute names, attribute properties appear with the values of the last selected block instead of “various”. I do not know if this is a “bug” or developer option, but “various” would be better in my opinion.

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

Available keyboard shortcuts


Task Details

Task Editing