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!

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.

Hallo Andrew,

I have revised the PWM Post Processor to Revision D.

Hallo Andrew,

Found a bug in the 3D Simulator execution

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.

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.

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,

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

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.

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

command line arguments: allow class name after -exec

It would be nice if one could select multiple blocks in the block list at once (holding ctrl or ctrl+shift). Main purpose would be to delete them if they are not needed anymore. If possible, the same applies to layers.

Wouldn’t it be nice, if selecting a block in model view would somehow highlight (just like clicking a block in the list does) the selected block in the “Block List” window?

(Feature request sounds a little harsh, enhancement proposal would seem more apt.)

I think it would be nice to have more flexibility for Prefix etc. option (not only the drop down with a given choice) and a remember function for all those fields like postfix and tolerance.

Why Remember Function:
If I use a postfix like <>” in the postfix field I’m only able to use it for this particular dimension type at this time. If I change the type (from Horizontal to vertical or what ever) I have always to repeat my postfix. The same with tolerances.

Blocks: moving complex blocks with drag and drop should show bounding box as preview

There is an issue importing from Autocad:
lines and quotes (both arrows and text) appear too much big (see attachment).
I can fix quotes modifying dimensions in “current drawing preferences”, but lines are still too thick.
Autocad’s dxf are opened with right line thickness but wrong quotes.
Furthermore, Autocad opens Qcad’s dxf files showing wrong quotes.

Select lines, arcs, ... and convert them to points along the lines, arcs, ... with a fixed distance.

See also forum at:
http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1834

Beispiel:
Zeichnen einer Linie (Line two points) mit Punktbestimmung.
Wähle ich für die Punktbestimmung z.B. “End” bleibe ich in diesem Modus bis ich etwas anderes wähle. Gut

Wähle ich für die Punktbestimmung “Intersection manual” muss ich dies für jeden Punkt immer wieder neu anwählen. Schlecht

The selection tool is not accessible:

Click on Selection Tool icon - left panel:

Left panel then shows line tool options.

Click “back” button at top of left panel:

Left panel then shows selection options.

Click an option icon:

Left panel then shows line tool options again.

Ziehe ich mit der Maus eine normale Auswahlbox kann ich Elemente markieren.
Möchte ich einzelne Bereiche wieder herausnehmen muss ich alle Elemente einzeln anklicken (mit gedrückter Shift Taste).
Ich kann zwar dies komfortabler gestalten mit der Select → (De -) Select Contour Funktion welche aber erst über das Menue aufgerufen werden muss.

So wie ich einzelne Elemente mit der Maus auswählen und mit der Shift-Maus Funktion deselektieren kann wäre es schön wenn die Shift Taste auch bei Auswahlbereichen direkt zum deselektieren eingesetzt werden könnte.

As an old professional “documentation writer and user inteface designer” but IMHO, I’m not convinced that the “Application preferences” are correctly organised for ease of understanding and using them.
These settings are organised in 2 levels. Some of the first levels have their own settings (e.g. “Graphics view”) while most others don’t (e.g. “Load/save”). May I humbly suggest some consistency rules :
- no sub-level if there is only one subject
- no items on main level if there are already 1 or more sub-level(s).
For instance :
- sub-level “Default Dimension settings” under “Dimension” is the only sub-level : then move these items under main level “Dimension” and suppress the sub-level ;
- the items under “Graphics view” main level (with several sub-levels)could be in a sub-level named “General” ;
Actually, “Graphics view” main level is the only one which has both its own items and sub-levels )) ?

Es wäre Arbeitserleichternd wenn ich bei den Optionen für Bemaßungen (Prefix/Postfix) eigene Präferenzen speichern könnte so das diese in allen Zeichnungen von mir verfügbar wären.
Zudem wäre es wünschenswert dieses nicht nur bei den Prefix sondern auch bei den Postfix Angaben nutzen zu können was dann alle(?) Manipulationen erschlagen würde.

Siehe auch:
http://www.ribbonsoft.com/rsforum/viewtopic.php?f=11&t=1966

Es wäre schön wenn ich Werte wie zum Beispiel Längen von Linien direkt abgreifen könnte um diese weiter in Berechnungen verwenden zu können.

Beispiel:
Ich habe eine Linie konstruiert wobei sich eine Länge y ergeben hat.

Nun möchte ich eine Linie zeichnen die 5 mal y sein soll.

Linientool → Wert 5* eingeben und y durch Auswahl mit der Maus von dem vorhandenen Elements übernehmen.

Natürlich könnte ich die Geometrie Info benutzen um den Wert abzulesen oder auch über die Zwischenablage zu benutzen. Ein abgreifen mit der Maus wäre aber schneller, direkter und wahrscheinlich auch mit weniger Fehlern (Human error) verbunden. Wahrscheinlich auch genauer da QCad, denke ich, mit mehr Nachkommastellen rechnet, oder?

Feature request
See topic - http://www.ribbonsoft.com/rsforum/viewtopic.php?f=31&t=2015

Just a thought, but one that could be useful for machinists in particular - a measurement tool that can snap to a point as per usual, but then just displays the drawing coordinates in X and Y. This could be expanded to the dimensions tool set, so that you can click on a point and print the coordinates next to it.

I would appreciate an option for the library Browser that gives me the possibility to decide by my self to use the current (same name) layer in my drawing or overwrite it with the existing layers in the library item.

Imagine the possibility’s of this feature ....

Different dimensions font sizes in the same drawing.

Support disproportional scaling also for arcs, ellipses, other entities, not only lines and polylines with only line segments.

Provide keyboard shortcuts for options tool bar.

Under Linux, Windows Alt+Key shortcuts can be used.
Mac OS X does not seem to support this.

See also suggestions at:
http://www.ribbonsoft.com/rsforum/viewtopic.php?f=32&t=2053&view=unread#unread

Wenn ich eine Zeichnung plane überlege ich mir natürlich im Vorfeld welche Blattgröße und welchen Maßstab ich verwenden möchte.

Wenn ich Templates (z.B. Zeichnungsblatt A4) für die Blattgröße öffnen könnte und dabei direkt einen Skalierungsfaktor (z.B. 10) vorgeben könnte hätte ich ohne Umwege gleich alles was man braucht. In diesem Fall ein A4 Blatt im Maßstab 1:10.

Im Grunde genommen das selbe was ich bereits mit Library Items machen kann ...

1. The Scrollbars for each window in the Viewports has the same size like the normal used scrollbars for windows. If you are working on a normal size Monitor it “steals” a lot of “working space”. Is there any possibility to make the scrollbars smaller or just a line to separate the windows so that I have to navigate with Keyboard and mouse?

2. I thing the Viewports and the View List belongs together - is it possible to get a button in the “View List / Tool Bar” to choose a Viewport style instead of “walking” the long way over the “Drawing preferences” Menu?

See also:
http://www.ribbonsoft.com/rsforum/viewtopic.php?f=47&t=2071

It would be useful if a file of keyboard shortcuts to commands could be loaded.

Then a set of shortcuts identical/based on the Autocad keyboard shortcuts can be loaded, making it much easier for Autocad users to migrate to your product.

There does seem to be some future functionality planned here, with the shortcut ‘scheme’ selector in Program Preferences, but for the moment ‘Qcad’ is the only option available.

This strategy is used to great effect by Draftsight (but who trusts a big company like Dassault/Solidworks...)

Command ‘Lengthen LE’ will extend most arcs but not all (2 arcs in the attached drawing do not work)! There is no obvious reason for this from the users point of view.

Drawing Unit is in “Inch” but the Layer Data (Line wight) is in “mm” ....

I like it ... but maybe I’m the only one

A line with linestyle = dots and line weight = 0.00 appears in model space overly spaced, all other lineweights behave as expected.
Suspect other linestyles to behave in a similar fashion.

See attached drawing.

Suggested fix: use the same scaling for lineweight 0.00 as for lineweight 0.05.