QCAD Bugtracker

If you spot an error in the translated user interface of QCAD, please add a comment to this task or submit your translation at http://translate.qcad.org.
Thank you for your help!

Wenn Sie einen Fehler in der übersetzten Benutzeroberfläche von QCAD erkennen, fügen Sie bitte einen Kommentar zu diesem Report hinzu oder geben Sie Ihre Übersetzung ein unter http://translate.qcad.org.
Vielen Dank für Ihre Hilfe!

Si vous remarquez une erreur dans l’interface utilisateur traduite de QCAD, veuillez ajouter un commentaire à cette tâche ou soumettre votre traduction à http://translate.qcad.org.
Merci pour votre aide!

Si detecta un error en la interfaz de usuario traducida de QCAD, añada un comentario a esta tarea o envíe su traducción a http://translate.qcad.org.
Gracias por tu ayuda!

Se si rileva un errore nell’interfaccia utente tradotta di QCAD, si prega di aggiungere un commento a questo compito o di inviare la traduzione a http://translate.qcad.org.
Obrigado por sua ajuda!

Se você detectar um erro na interface de usuário traduzida do QCAD, adicione um comentário a esta tarefa ou envie sua tradução para http://translate.qcad.org.
Obrigado pela sua ajuda!

Als u een fout ziet in de vertaalde gebruikersinterface van QCAD, voeg dan een opmerking toe aan deze taak of stuur uw vertaling naar http://translate.qcad.org.
Bedankt voor uw hulp!

Andrew,

I know that GCodeMM.js and GCodeIN.js are generic postprocessors.
Mostly used as base for other or custom postprocessor.

The distinct nature is pretty clear from the filename and the suffix in the display name.
Another distinct nature is that they include this.unit = RS.Millimeter / RS.Inch intended for the CAM side.

Why don’t they include at least a G20/21 in a generic header?

There are several more specific postprocessors where I miss these G-codes for the measurement system.

True, if they are not supported, no error messages would occur when omitted.
The danger is that users rely on build in postprocessors hoping that it matches with the default measurement system of their setup.

IMHO it is safer to trigger an instruction fault before attempting to execute a wrong motion.
As fail-save as possible should always be the goal.

Regards,
CVH

Hi Andrew,

Creating G-code for cnc-laser, the laser-tool can not be correctly set at all.

Attached a laser tool proposal

Add SPx; with x being pen number from 1-8.

TODO:
- Which color corresponds to which pen number?
- What if there are more than 8 colors in a DXF files?

Hi Andrew,

Still working with and on CAM HPGL for the HP7580 pen plotter.

I have added a penplotter test drawing, that might be used for testing en callibrating plotter and pens. You may add it to the Examples-directory.

QCAD has a lot of trouble creating toolpaths and exports. Much too often it shuts itself down, or gets stalled. Why? I am not sure.

Hi Andrew

QCAD/CAM misses a hpgl.plt import. If gerber and G-code can, so should plt.

Hi Andrew

A request for adding some fields to the toolpath

Hi Andrew,

Still working on creating HPGL.PLT toolpaths for the HP7580 pen plotter. QCAD has some trouble creating toolpaths. Too often it shuts itself down, or the PC gets stalled.

Recreating the same error however is possible

Hallo Andrew,

I am still busy on the never ending G-code story. Doing so I wrote a small Post Processor Tutorial for all those nerds who wants to write their own. If you like it you might add it to QCAD. However, since English is not my native tongue I suggest checking it would be wise.

Meanwhile I have downloaded the source code, and could not find the CAM’s Drill-path-script. I am now using a negative Drill Cut Depth to set a Laser Dwell time, were as a field “Dwell Time (in seconds)” in the Drill-path would be more appropiate. Is this script open source available or is it part of ‘closed part’ of QCAD?

Hallo Andrew,

Still busy on the never ending G-code story. Urgently needed the very common Traverse Toolpath.

Example added as pdf.

Greetings

Hallo Andrew,

Still busy on the never ending G-code story. Urgently needed the very handy G-code Block Toolpath. This ‘toolpath’ also solves a lot of “editing requests”.

Hallo Andrew

It would be more than conveniant, defining the drilling locations of the drill toolpath, by selecting a circle’s center point.

Hallo Andrew,

testing the drill toolpath I used single point markers.

In 3D simulation the tool drills the toolpath AND uses the drill as a mill.

Cam Export and generated G-code is not effected.

Add a program description to the CAM configuration dialog and export to postprocessors as variable.

See also:
https://www.qcad.org/rsforum/posting.php?mode=quote&f=32&p=24649

Hallo Andrew,

I have revised the PWM Post Processor to Revision D.

Hallo Andrew,

Found a bug in the 3D Simulator execution

With a Mac (and no external mouse) there’s no middle button so it’s not possible to pan the 3D view (that’s what they tell me in the forum). It would be useful if one could use command-drag or control-drag to pan around the 3D view.

QCAD/CAM
Trial package Win installer 32 bit
Version: 3.25.2.0 (3.25.2)
Internet: QCAD.org
Build Date: Sep 4 2020
Revision: 4a61501
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Local decimal separator is ‘,’ (comma)
In CAM configuration .. Z Levels .. Safety level

Using nn,nnn the output is Nxx G0 Znn
Using nn.nnn the output is Nxx G0 Znn.nnn

Drop down boxes are all in dot format.
Didn’t try anything else yet

Regards,
CVH

Hello dear CAM developers!

I need to use the same tool at different spindle speed in a single machining file.
I would deeply appreciate if you could add a Spindle Speed edit field in the CAM Profile Toolpath edit window in order that each Toolpath can have its own Spindle Speed value (same as you did for Feed Rate and Plunge Rate)

FYI, the tool on my concern is a laser who’s power is driven by the Spindle Speed PWM signal.
I need to be able to do both engraving and cutting in a single file.
Alas! this laser tool is defined with a fix and unique number (99).
Therefore I cannot define different laser tools with different speeds.

Many thanks
Best regards.

I’m often in the situation that I have to select for nesting 50+ sheets. Currently is only a Shift + left mouse click selection possible. It would be nice if QCAD/CAM could get for the nesting / sheet selection additional a mouse rectangle area selection.

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

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

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.

When editing an existing toolpath to update the parameters of the selected tool, we can update the Feed Rate and the Plunge Rate, but I couldn’t find any way to update the Spindle Speed.

Even when using the Edit Tool KE button, we can edit parameters of the tool on concern but none of the modification is applied to the current Toolpath because as I see, tools parameters are copied fron tools definitions to a Toolpath only at creation of this Toolpath, but Toolpath are not updated accordingly.

Could you please add an edit field for Spindle Speed in the CAM Profile Toolpath window?

Many thanks’, and best regards.

Andrew,

Unrelated to OS or QCAD version.

In the postprocessor configuration dialog there is a group box called ‘GroupCustom’.
One can add custom widgets to that, rename it and so on.

Such is not provided in CamProfileToolpathDialog.ui or CamDrillToolpathDialog.ui

It should be possible but we aren’t really able to mix up things with the ‘Message’ QLabel ...
A reserved QGroupBox would do the trick.

Related topic:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=9647

Regards,
CVH

Related forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10468

For ‘milling’ on path it doesn’t consider

this.arcInterpolation = true

in the custom postprocessor nor the checked option in the CAM Configuration Dialog.

As far as detected the CamArcInterpolation checkbox of the CAM Configuration Dialog is unrelated to the this.arcInterpolation in the postprocessor.

Regards,
CVH

I’ve been able to make this work as proof of concept very easily, but many of the functions are inaccessible/difficult to override from post-processors.

Desired functionality:

1) Enable “Add Profile Toolpath” UI elements all the time (remove setRequiresSelection)
2) CAM Profile Toolpath Dialog: Drop-down menu of available Layers. First option “By Selection Only” 3) “By Selection Only” continues to pass EntityIds of selected objects (existing functionality)
4) Choosing an active Layer will use the Layer as source of EntityIds
5) Any changes to Entities on a Layer will result in those new/removed/changed objects being re-generated without having to manually select and update the tool paths. Either do not recover list of EntityIds from the ToolpathBlock, and instead use “live” each time it’s regenerated, or additional functionality to determine if a LayerId is associated with the Toolpath, and then lookup EntityIds.

I assume the persistence of the Layer selection would be available within the Toolpath, so that it will automatically update EntityIds every time a Toolpath is regenerated, without having to select Entities and updating the toolpath manually.

For large projects, being able to force select objects based upon layer dramatically reduces mistakes and speeds up the workflow.

Thanks

Andrew,

At present QCAD/CAM the tool drop-down box displays tool number and diameter between brackets.

It would be more appropriate to display if it is a mill or a drill and/or the description of such.
In a further stage of development ball-nose ... Conical ... And so on.

I have several specialized mills with the same diameter.
End-mills, roughing mills, routing mills, face mills ....

Tools 1(ø6mm) or 2(ø6mm) don’t say much if tool 1 is a side-mill and tool 2 is a high speed drill for metal.

Related forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10722

Regards,
CVH

Andrew,

Please refer to related forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10724#p44206

An eighth circle with radius 8 Lead In/Out relates to nothing in the actual exported cutter trajectory.
Nor does it with the edge being cut.

Proper examples and a comparison with ‘Extension’ type Lead In/Out included.
Conclusion: IMHO connecting the cutter trajectory and edge being cut is wrong.

It looks a lot like turning on Cutter Compensation (G41/42) while the motion is circular.
But that is uncommon because most controllers can not cope with this motion.
One can increase the offset gradually along a straight pre-entry segment for turning on G41/42 but not along a circular path.
Also see snippet:
- Pre-entry C→B turning on G41
- Circular Lead In B→A

Regards,
CVH

Building with the bundled version, 1.8.5, works fine.

When I try to build using the system version, which for Mageia Cauldron is 1.9.3, the build fails.

https://raw.githubusercontent.com/kekePower/mmbl/master/qcad/2019/12/11/20%3A13%3A48/log.qcad

Here is the current spec file for version 3.23.0.4.
https://svnweb.mageia.org/packages/cauldron/qcad/current/SPECS/qcad.spec?revision=1465894&view=markup

It looks like qcad is incompatible with versions above 1.8.5.

Are there plans to port to the new version?

Thanks in advance.

How to reproduce.

1. Create a text field with some non-english words in the upper index. (see attached pic1.png)
2. Save the project and close QCAD.
3. Run QCAD and open same project.
4. Now upper/lower indexed text becomes not human readable UTF codes. (see attached pic2.png)

Tried different fonts - doesn’t help.

Linux ntb-kirill 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
CentOS Linux release 7.7.1908 (Core)

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
(

no task description

The dark theme for Linux is broken:

- Some icons have dark background (expected) and black foreground color (that should be replaced by white of very light gray)
- Some icons have light background (not cohesive with the theme).
- The command history shows dark blue font on dark gray background.
- The grid’s ruler shows black font over dark background for the numbers.
- The icons folder is missing in the GitHub repository, but other themes have that folder.
- The general icons (open, save, and so on) are not dark theme friendly. A better approach for maybe all the themes would be to use something like the breeze icons pack for LibreOffice, and it will have the added benefit of making the app look more modern.

The icons issue is the biggest problem. They should probably replace the black color for white or very light gray. Even the red accent color is not ideal for dark themes, is not the main issue.

Attached is an image that show the problems and another that shows LibreOffice with the Dark Breeze theme for reference.

I’m using QCAD Community Edition 3.27.7 on Windows 11.

When I started my drawing, I was able to change the size scale factor of (existing) dimensions using “Edit/Drawing Preferences/Dimension/Dimension Settings/Size scale factor”. However, suddenly this feature stopped working and now I cannot switch the dimension scale factor any longer.

I used this feature to be able to adapt the scale factor of the dimensions when printing in different scales.
I.e. all my drawings are in “original” size but when it comes to printing, I print some parts in scale 1:2 (in which case I used to set the size scale factor of the dimensions to 2) and some parts in scale 1:10 (in which case I used to set the scale factor of the dimensions to 10). Using this procedure, the dimensions have the same size (font size, arrow size, gaps etc.) on both drawings.

I have attached the drawing, that shows the described issues.

The 3dConnexion Space Navigator would be wonderful as a pan and zoom control. I find it extremely useful in SketchUp and when I switch from that to QCAD am always disappointed to find it doesn’t work.

3dconnexion DOT com/buy/shop.html?3dxcp=GA_GA_search_google_US_Brand

While full support for the buttons and such would be nice, just the ability to map the axis to pan and zoom would be wonderful.

Property Editor - Geometry - Custom - Add Custom Property

If I use an identical Name accidentally again in the Custom Property dialog - it will overwrite the first value with the same name without any warnings.

Status Bar menu remains unchecked even it is toggled on or off

Hi Andrew,

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

Regards

Clive

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

QCad 3.19.2 Professional, 64bit, Liux Mint

Case:
1. Open some saved drawing with viewport entities on layout block (paper space). Print Preview mode is “On” automatically.
2. After “File-Revert” drawing is reopened on layout block (paper space), but now Print Previw mode is “Off” .

For example can try on “flange.dxf”

Drawing converted from inch to mm - undo leads to wrong dim label position. I can fix that with “Reset Label position” but it would be nice if QCAD could to that in first place.

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:

My data files are stored on network shares (synology) with a GB link. QCAD Pro is run in Admin mode.

While in my Windows browser all remote shares are accessible (Green), in the QCAD file open menu they are initially shown as not accessible (Red). By accessing a specific drawing file in a remote share, the share will open and turn green.

Same behavior using ‘Open recent’. Always the message is given that the requested file does not exist, and the file is wiped from the ‘Recent Open’ list. Only if the share is first accessed through ‘Open’ with a random file, it will turn and a ‘recent open’ file for that share will open.

Drag and Drop from a remote share will never work.

See also:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=6367#p23947

See also:
https://www.qcad.org/rsforum/viewtopic.php?f=89&t=6447

Win7pro 32bit Qcad 3.23.0

Andrew,
The Arc segments of Polylines with Global or any Local Width render faulty where Global Z or any of the arc’s local Z is not zero.

In the attached drawing setting the Global Z of the inner poly to 5,10,...

The setting of Z to not zero affects the radius of the projected arc and not the bulging of the poly.
It also affects the projected widths of the line inversely, but not by changing the widths properties.

Pritty rare combination! True.
Qcad is 2D native! True.

Flatten will resolve this.

It is not a purely visual rendering fault, the poly will explode as such.

Maybe similar flaw as with uneven scaling blocks with arcs.
https://qcad.org/rsforum/viewtopic.php?f=8&t=5566#p20703

Regards

Yesterday I set up a Windows 64 bit install of QCAD Pro which shows the same bug I have been seeing for a while in the Community linux git repo.

Create a new drawing and then go to “Print preview”. Enable “Move paper postion”, the cursor changes to the hand icon, but the paper position is unable to be moved. Only by saving the drawing, exiting the program, restarting and reopening the drawing, will the “Move paper postion” function correctly.

Affected versions tested:

Windows 64bit installer download, as of yesterday.
Linux 64bit build from git, about 20minutes ago.

For what it’s worth, this bug is not present in this previous git checkout:

Version:
3.21.1.0 (3.21.1)
Internet:
QCAD.org
Build Date:
Jul 2 2018
Revision:

Qt Version:
5.7.0
Architecture:
x86_64
Compiler:
gcc 6.3.1

Thanks for a great product.

Openning a big file or doing any action in it, takes minutes to load.
Even dragging the scrollbar slightly left or right, takes mintues to redraw the canvas again, which makes QCAD un-usable for professional use.
Is there a way to make QCAD usable, after loading completed:
- Like suppressing edit until user says so,
- or taking snapshots of rendered canvases to another file and use it, as windows uses thumb.db ( for negative latency :P )

PS: I wish I could help a bit, but my hand are tied. I am just a java freak, I am opt to any idea of porting it to java, if she is still alive.

Tuğalsan Karabacak
EEE, MSc Mobile Comp & App, IWE

QCAD 3.24.2 / macOS x86_64 10.14.6

Starting with empty doc:
1. Draw any object (e.g. a rectangle) on layer 0.
2. Create new layer (”1”) with color, say yellow.
3. Select new layer
4. Select new object
5. Modify → Move / Copy
6. Click reference point
7. Click target point same as reference point
8. In “Move / Copy Options” dialog, select “Delete Original” and check “Use current layer and attributes.” Click OK.

The moved object stays on the layer it was previously on. Using “Move / Copy” as a quick way to move a selection between layers is not useful even though it appears to be the recommended way in a Google search.

Note: if “Keep Original” is selected instead, the copied object is placed on the current layer and the original object remains on its layer, as expected.

Note: if the target point is different from the reference point, the moved object is placed on the current layer as expected.

There are other workarounds too, cut / paste with “To current layer” checked seems to work, as does chaging the layer in the Properties Editor.