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 TypeSeverity  descSummaryStatusProgress
1132QCAD (main)Feature RequestVery LowInfo > Polygonal Area: create blockAssigned
0%
Task Description

Optionally create an (anonymous?) block for the polygon and the text.

1154QCAD (main)Feature RequestVery LowAdd preference for round reference pointsAssigned
0%
1 Task Description

This one is purely cosmetic, instead of square reference points would it be possible to have the choice of either square or round with size?

1227QCAD (main)Feature RequestVery LowAutoCAD skinAssigned
0%
Task Description

QCAD has a lot of features and buttons, probably more that the autocad I’ve been using. Therefore the learning curve is too slow. It would be a great boost for the program to have the possibility of having an Autocad skin, and it will attract many new users.

1426QCAD (main)Feature RequestVery LowLoad drawings that were open when closing QCAD on start...Assigned
0%
Task Description

See also:
http://www.qcad.org/rsforum/viewtopic.php?f=31&t=4249

1626QCAD (main)Feature RequestVery Low'Clip to Circle' toolAssigned
0%
1 Task Description

Hi Andrew,

Would it be possible to have a clip to circle tool also please?

Regards

Clive

1649QCAD (main)Feature RequestVery LowAdd configuarable format options for saving blocks to l...Assigned
0%
Task Description

Add configuarable format options in application preferences for saving blocks to library to either dxf or dwg.

1788QCAD (main)Feature RequestVery LowAllow snapping to reference point of a block referenceAssigned
0%
Task Description

I know this was reported and fixed before ...

https://www.qcad.org/bugtracker/index.php?do=details&task_id=843

... but it looks like we have the issue now back with some kind of variation.

If I use the test drawing which I posted in 2013 ( FS#843 ) it works still as expected after it was fixed.

If I create a new block it won’t work in a new drawing nor in the old test drawing - no chance to snap to the Block Reference.

Edit: New Test drawing:

1056QCAD (main)RefactoringVery LowDead and wrong code in RSPlatform.cppAssigned
0%
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 );
 #endif

(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.

Thoughts?

1324QCAD/CAMSuggestionVery LowConfusing Copy / Move optionAssigned
0%
Task Description

Hi,

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
0%
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.

Jean-Claude

1607QCAD (main)SuggestionVery LowIndent 'Spline Segments:' in explode preferencesAssigned
0%
1 Task Description

 FS#1604  was issued because of non-intuitive hierarchy of the preferences for the Explode function.
The task comment recieved explains the funcionallity in details not found elsewhere.

Indentation of the phrase ‘Spline Segments:’ suggest hierarchy.
Graying out the drop down box for the number of spline segments establish hierarchy.

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

Available keyboard shortcuts

Tasklist

Task Details

Task Editing