QCAD Bugtracker

QCAD. ver. 3.27.1.0 (3.27.1)
Qt version: 5.13.2
Architecture: x86_64
OS Windows 11

It might be useful to have the possibility to manage the references of the images contained within the drawing. A design could use recurring images, stored in a folder outside the one in which the design is located. Moving the drawing or folders (or changing the PC) will lose the folder references and the images are not displayed when the drawing is opened again.
I imagine the possibility to view the references of the images (and if necessary modify manually or with a pointer) with the option of: attach, detach, reload, etc., as in the example below (referred to ActCad - based on Intellicad technology)

Referring to Layer List / Block List: It would improve the workflow if the Delete key on the keyboard would be linked to the minus icon (Delete). The command ER is also ignored in both list.

It would be nice to have the possibility to select multiple blocks with Shift and/or CTRL + mouse like the Layer List to use a delete etc command on all selected blocks at once.

QCAD (before version 3.27?) used to show some custom XDATA, e.g. tag 1000, even for application names that are not “QCAD”, which for me was useful, so it’s somewhat of a regression. (I think it was broken when selecting multiple items, maybe that’s why it was removed.)

I suggest to bring that feature back, but maybe show it only when a single element is selected if that’s easier.

(As a workaround/hack I guess it would be possible to rewrite the required information as QCAD compatible XDATA externally I guess.)

As per https://qcad.org/rsforum/viewtopic.php?f=32&t=9089, I suggest to extend the distance information tools:

* show Delta Z (at least when any of the elements has Z information)
* allow switching between 2D and 3D distance
* maybe allow to show both
* maybe change the text to distinguish between them (”Distance” → “Distance 2D/3D”)

“em” just always goes back to the main drawing. But for nested blocks, when jumping from edit mode of one block to the next nested block, it would be helpful to have some “ep” to go back to the previous block.

This was discussed at the forums...

Currently if I position one Tab (KT) to stacked profiles QCADCAM will use it on ALL in Z matching profiles. Practically in most cases would be to use tabs only on the lowest profile.

It would be nice to have some kind of control on which profile a tab has to be used.

Please refer to: https://www.qcad.org/rsforum/viewtopic.php?f=74&t=9033

Regarding to forum post:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8982&p=35836#p35836

dwg loaded in 3.27.1 frees QCAD (no response) and a Win10 PC. Same drawing loaded in 3.26.0 causes no problems. It looks to me that two hatches (handle 198b6, 198ba) are the culprits.
Drawing saved without those hatches opens without any problem in 3.27.1.

TECNOFLEX symbol library.dwg = original file from forum post
TECNOFLEX symbol library_mod.dwg = my modification

Headline should already explain the issue ...

1. Create spline
2. Move spline nodes. After ~10 times move qcad is crashed with backtrace:
Thread 9 “Thread (pooled)” received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff56dc9640 (LWP 8224)]
0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848) at /usr/include/qt5/QtCore/qlist.h:492
492 current→v = new T(*reinterpret_cast<T*>(src→v));
(gdb) bt
#0 0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848)

  at /usr/include/qt5/QtCore/qlist.h:492

#1 QList<QSharedPointer<RShape> >::detach_helper (alloc=<optimized out>, this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:835
#2 QList<QSharedPointer<RShape> >::detach_helper (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:849
#3 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178
#4 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178
#5 0x00007ffff686182a in QList<QSharedPointer<RShape> >::end (this=<optimized out>, this=<optimized out>) at /usr/include/qt5/QtCore/qlist.h:342
#6 QList<QSharedPointer<RShape> >::last (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:364
#7 RSpline::appendToExploded (this=0×555557311510, line=...) at math/RSpline.cpp:964
#8 0x00007ffff6867059 in RSpline::getExploded (this=0×555557311510, segments=1457293328) at math/RSpline.cpp:919
#9 0x00007ffff686682a in RSpline::getLength (this=this@entry=0×555557311510) at math/RSpline.cpp:1026
#10 0x00007ffff6c11490 in RSplineData::getLength (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineData.h:178
#11 RSplineEntity::getProperty (this=0x5555573114a0, propertyTypeId=..., humanReadable=<optimized out>, noAttributes=<optimized out>,

  showOnRequest=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineEntity.cpp:253

#12 0x00007ffff67cc214 in RPropertyEditor::computePropertyValue (ccProp=...) at /usr/src/debug/qcad-3.27.0.0/src/core/RPropertyEditor.cpp:574
#13 0x00007ffff67d298f in QtConcurrent::FunctionWrapper1<void, RProperty&>::operator() (u=..., this=0x555557757f18)

  at /usr/include/qt5/QtConcurrent/qtconcurrentfunctionwrappers.h:80

#14 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIteration (it=..., this=0x555557757ee0)

  at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:68

#15 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIterations (this=0x555557757ee0,

  sequenceBeginIterator=..., beginIndex=<optimized out>, endIndex=15) at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:77

#16 0x00007ffff67d2c9d in QtConcurrent::IterateKernel<QList<RProperty>::iterator, void>::forThreadFunction (this=0x555557757ee0)

  at /usr/include/qt5/QtConcurrent/qtconcurrentiteratekernel.h:255

#17 0x00007ffff44b5b2d in QtConcurrent::ThreadEngineBase::run (this=0x555557757f20) at qtconcurrentthreadengine.cpp:302
#18 0x00007ffff59c8d52 in QThreadPoolThread::run (this=0x555556198b10) at thread/qthreadpool.cpp:100
#19 0x00007ffff59c5a61 in QThreadPrivate::start (arg=0x555556198b10) at thread/qthread_unix.cpp:329
#20 0x00007ffff546c717 in start_thread (arg=<optimized out>) at pthread_create.c:435
#21 0x00007ffff54f018c in clone3 () from /lib64/libc.so.6
(

It would be helpful if the scale field that appears while placing a viewport would also re-appear when the viewport is selected after it’s already been placed in the layout. It would also be helpful if the pre-populated values in the dropdown matched those in the global layout scale field.

The inside corners of profile tool paths have rounded inside corners. This occurs because the rounded outside the bit cannot make it all the way into the corner of the feature. Think of tracing the inside wall of a cardboard box with a can of soup. The can makes direct contact with the box walls, but its
round shape is unable to completely fit into the tight corners— there’s always a gap.

In a dog-bone overcut (see the figure in attachment), the inside profile corner is enlarged into a semicircle, allowing the sharp edges of the mating piece to slide through without interference.

When a dog bone is applied to the inside corners, as shown in the second figure in the attachment, the joints fit together nicely!

The following website explains what should be implemented More elegant CNC dogbones

There are two ways to implement this tool. Either you modify the original design (as implemented in Fusion 360) or you can do it at the moment you define the tool path (Estlcam allows you to do this for example). See the feature Corner overcut, on Estlcam website

Hi,

I believe prior QCAD version 3.22.0.0 there was no rotating preview. The rotating preview shows the outcome regarding to the chosen center point. I know that it is also common for move/copy. However, for me it is very confusing and difficult to chose the correct center point for a rotation if I’m constantly been distracted by the most of the time overlapping preview of my selection. This said if the drawing is very detailed I have to zoom in extremely to be able to snap to the right entity. That wouldn’t be necessary without the preview. Additional rotate a large drawing selections will compromise the performance - CPU is going like crazy.

It would be nice to have an option to turn this preview on/off.

Add a tool to duplicate a layout block with contents.

Multiline attributes can contain linefeeds and formatting like MTEXT.

Would be nice to change default font type and size for command line widget.

I’m used to have persistant selection while drawing (Application Preferences > Graphics View:Appearance > Selection), but I’m missing deselection of all objects with ESC key. I have seen the option to deselect with right key, but it’s nice to have right key for context menu.

Currently ESC key cancels current active command, but would be nice if there is no command active to also deselect all features by default.

I tried to assign double click on middle-mouse button to zoomauto command, but it seems it’s not possible currently.

Would love to see this feature.

Would it be possible to extend the tool for importing points with a label so that when importing points into the drawing (as it is now), the attributes of the point are taken from the csv file and written to the point’s own properties? See attachment. This would extend the functionality of the tool and I assume that it would also lay the foundation for the possible re-export of such points from the drawing to a csv file, including all the details.

When using the vertical line tool, you can enter a length value in the options toolbar, then place the line. If you want to change the length, you just need to enter a new value and the length field will update. However, there seem to be cases where after 10-20 entries, the focus goes off the length field in the options toolbar, requiring the user to bring focus back to continue. I could not seem to duplicate this behavior with the horizontal line tool.

The option of a layer state widget would be a nice way to see and select between different layer states.

I have set the grid/snap value to X=.0625 Y=.0625 on all 4 viewports.
When zooming in and out the grid/snap scale changes from .0625 to 3.90625. at this point the grid/snap points differ,
This causes a variation in the grid/snap reference points lending to drawing errors.

example
When I use the grid settings defaults .01, when zooming in and out, the grid/snap scaling doesn’t seem to have this issue.
Other values do, See below.

set value first zoom second zoom next zoom

	point		point		point ...	

0.01 0.1 1.0 10.0 ...
0.02 0.04 0.4 4.0 ...
0.04 0.16 1.6 16.0 ...
0.05 0.25 2.5 25.0 ...
0.0625 0.390625 3.90625 39.0625 ...
0.0254 0.64516 6.4516 64.516 ...

Why is there a squaring of the original set value? Which then becomes a new zoomed grid/snap value?

QCAD Professional
Version: 3.26.4.0 (3.26.4)
Internet: QCAD.org
Build Date: Jun 3 2021
Revision: 0bb4334
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

As a heavy mechanical drawings user, it would help a lot to have an option to exit a block saving as a new name and making it a new entity from that time ahead.

Example: if a have a lot of screws, one of then is behind another peace and need the to have some lines changed to hidden style lines, in the flow of the work is great if I edit that screw in place and when exiting have the option to save as a new block, to don’t mess with other entities of the same block that I don’t want to change. Yes, there is a workaround that is duplicate and rename the block prior to the editing, but a save as seems to work easier.

Thanks Andrew and team!

In the US, it is (unfortunately) still common to use US survey foot. It seems at least some DXF applications/libraries support this unit as a $INSUNITS value, some references:

• https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2020/ENU/AutoCAD-Core/files/GUID-A58A87BB-482B-4042-A00A-EEF55A2B4FD8-htm.html
• https://ezdxf.readthedocs.io/en/stable/concepts/units.html#insunits

There are two issues regarding this with QCAD:

1. If you open a document with $INSUNITS being 21, it’s reset to 0 (unitless/unspecified) when saved again, even when not changing anything.
2. It is not possible to select these units in the GUI.

I don’t know about standardization of these values, but my hope is that it’s at least possible to preserve the unit in an existing drawing. Given that this unit is supposed to be obsolete in some years, it might seem less important, but due to this transition, it might get even more important to be able to distinguish between units. Thanks!