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)

IDCategory  descTask TypeSeveritySummaryStatusProgress
513TranslationBug ReportLowTranslation errorsAssigned
0%
Task Description

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!

2507QCAD/CAMFeature RequestLowAdd Toolpath from LayerAssigned
0%
1 Task Description

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

2506QCAD/CAMFeature RequestLowInclude arc segmentation for 'milling' On-Path.Assigned
0%
3 Task Description

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

2418QCAD/CAMFeature RequestLowInclude a GroupCustom widget in CAM Toolpath dialogs.Assigned
0%
2 Task Description

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

2374QCAD/CAMFeature RequestLowAdd Spindle Speed to Toolpath DialogAssigned
0%
1 Task Description

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.

2331QCAD/CAMFeature RequestLowTabs: Control over on which particular profile used.Assigned
0%
Task Description

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.

2330QCAD/CAMFeature RequestLowToolpath optimization optional (on/off)Assigned
0%
2 Task Description

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

2307QCAD/CAMFeature RequestLowTools to create dogbones or corner overcut Assigned
0%
2 Task Description

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

2233QCAD/CAMFeature RequestLowMore selection options to select sheets for nestingAssigned
0%
Task Description

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.

2213QCAD/CAMFeature RequestLowAllow editing Spindle Speed separately for each Toolpat...Assigned
0%
1 Task Description

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.

2167QCAD/CAMBug ReportLowComma format decimal separator fails ZSafety CAM config...Assigned
0%
1 Task Description

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

2164QCAD/CAMFeature RequestLowAdd ability to pan the 3D view with a modifier key and ...Assigned
0%
2 Task Description

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.

1971QCAD/CAMBug ReportLowCAD/CAM 3D SimulatorAssigned
0%
Task Description

Hallo Andrew,

Found a bug in the 3D Simulator execution

1954QCAD/CAMReleaseLowRevised PWM Post ProcessorAssigned
0%
Task Description

Hallo Andrew,

I have revised the PWM Post Processor to Revision D.

1940QCAD/CAMFeature RequestLowCAM > CAM Configuration: Add program descriptionAssigned
0%
1 Task Description

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

1913QCAD/CAMBug ReportLow3D Simulation Behaves oddAssigned
0%
Task Description

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.

1911QCAD/CAMFeature RequestLowDrill ToolpathAssigned
0%
Task Description

Hallo Andrew

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

1902QCAD/CAMFeature RequestLowCAM G-Block ToolpathAssigned
0%
Task Description

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

1901QCAD/CAMFeature RequestLowCAM Traverse ToolpathAssigned
0%
Task Description

Hallo Andrew,

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

Example added as pdf.

Greetings

1877QCAD/CAMFeature RequestLowPost Processor TutorialAssigned
0%
Task Description

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?

1847QCAD/CAMBug ReportLowBUG MEMORYAssigned
0%
Task Description

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

1846QCAD/CAMFeature RequestLowToolpath preset offsetsAssigned
0%
Task Description

Hi Andrew

A request for adding some fields to the toolpath

1844QCAD/CAMFeature RequestLowHP/GL (PLT) importAssigned
0%
Task Description

Hi Andrew

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

1843QCAD/CAMBug ReportLowCreating ToolPath StallsAssigned
0%
Task Description

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.

1841QCAD/CAMFeature RequestLowQCAD/CAM Postprocessor "Hpgl": Add pen colors to HP/GL ...Assigned
0%
Task Description

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?

1815QCAD/CAMFeature RequestLowAdd Laser tool optionAssigned
0%
Task Description

Hi Andrew,

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

Attached a laser tool proposal

2405QCAD Community EditionBug ReportLowDimension scaling not workingAssigned
0%
Task Description

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.

2391QCAD Community EditionBug ReportLowFix Dark Theme for LinuxAssigned
0%
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.

2386QCAD Community EditionBug ReportLowLabel "Linear format" missing in Property EditorAssigned
0%
Task Description

no task description

2315QCAD Community EditionBug ReportLowCrash after ~10-th times move Spline nodesAssigned
0%
Task Description

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
(

2068QCAD Community EditionBug ReportVery LowNon-english text in upper/lower index becomes UTF codeAssigned
0%
Task Description

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)

2011QCAD Community EditionSuggestionVery LowUpdate QCAD CE SpatialIndex module to latest versionAssigned
0%
Task Description

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.

2552QCAD (main)Bug ReportLowWindows shortcut Alt + Underlined Key fails partly in m...Assigned
0%
Task Description

Reason: Same underlined keys are used for different menus

Select and Snap = S,
Dimension and Info = I,
Modify and Misc = M,

2551QCAD (main)Bug ReportLowCursor and visualization problemsAssigned
0%
Task Description

The last version (3.29.4) present a very important issue.
When we work with a “complicated” file (about >1MB or up see attachment test.dwg) the cursor and selected object not work fine after move some layout windows in Paper_Space: disappear coordinates informations and snap nodes. (see attachment before.png an after.png)
This issue is present in all Qcad version (Linux, Mac-intel, Mac-silicon, Windows).
The last working-fine version is 3.28.2
I’m a enthusiastic Qcad user and I hop that this issue will be fixed early!
Regards
Arch. Riccardo Beduschi

2550QCAD (main)Bug ReportLowOnly a partial hatch appears in a closed shapeAssigned
0%
Task Description

I’m seeing only a partial hatch in the shape. See here for details.

2547QCAD (main)Bug ReportVery LowBlock > Purge Unused Blocks > Removes _DatumFilled bloc...Assigned
0%
1 Task Description

Andrew,

The _DatumFilled Block used by Datum entities (DT) is considered as not used and is purged by Purge Unused Blocks (BP).
There is no block association for these special types of arrowheads in QCAD.

After purging the Datums are not immediately updated but the special arrowheads will eventually disappear. Adding new Datums will not fix that.

Not problematic because the _DatumFilled Block is re-created on save/reload when Datum entities exists. Datums are updated.

Probably not OS or version related.
Related forum topic: https://www.qcad.org/rsforum/viewtopic.php?f=89&t=10694

Best solution would be to support different types of arrowheads and all related:
https://qcad.org/bugtracker/index.php?do=details&task_id=695 https://qcad.org/bugtracker/index.php?do=details&task_id=757 https://qcad.org/bugtracker/index.php?do=details&task_id=1157

Regards,
CVH

2544QCAD (main)Feature RequestVery LowRequest to add "plain text" paste, traditionally CTRL-S...Assigned
0%
2 Task Description

See:
https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10379

Could you add “plain text paste” as ctrl-shift-V
Why? Because sometimes the clipboard comes in with rich text formatting that’s anti-helpful.
The workaround is to paste into a plain text editor, or the console, then recopy and repaste into qCad.

Either way the ctrl-shift-V shortcut is useful for those trained on other software but:
one could also argue that qCad should NEVER take rich text, and rather only accept the plain text with both CTRL-V and CTRL-SHIFT-V.

— CHV says

Agreed, having encountered it numerous times while documenting with text snippets from elsewhere. :roll:
Even copying Info measurements from the Command Line are Rich Text.

The best place to file a feature request is QCAD Bugtracker:
https://www.ribbonsoft.com/bugtracker/ You may need a different account there or make a new one.

May I remark that Ctrl-Shift-V is already in use for Paste along Entity (PE)
But not when the Text Editor Widget has the focus and dialog Widgets are always modal on a Win OS system. :wink:
Still, I’ll vote for it in any way.:P

Regards,
CVH

2543QCAD (main)Bug ReportLowPolygonal Area Tool (IR) creates shapes persistently, c...Assigned
0%
1 Task Description

Upon activating the Polygonal Area Tool either by clicking on the toolbar or by the IR keyboard shortcut the tool will persistently draw a polygon without clicking anything. This happens with the mouse and the trackpad on the MacBook Pro. This was happening in 3.29.3, and then after I upgraded to 3.29.4. The MacOS version is 14.1 Sonoma.

2541QCAD (main)SuggestionVery LowConsider the unit "Microinch" to be non-metricAssigned
0%
1 Task Description

Andrew,

One Microinch is equivalent to 25.4 nanometers and I don’t consider that to be metric.

RUnit.isMetric(this.getDocument().getUnit()) returns true for RS.Microinch or value 8.

https://github.com/qcad/qcad/blob/master/src/core/RUnit.cpp#L145-L155
Returns false for: RS::Inch ; RS::Foot ; RS::Mile ; RS::Mil ; RS::Yard
... and true for all the rest.

Also see last note in: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=9506&p=38295

Not to be confused with RDocument::isMetric() because that returns the measurement system unless that is RS::UnknownMeasurement what is rather impossible with drawings created by QCAD.

Regards,
CVH

2540QCAD (main)Feature RequestLowRetain original handle when Hatch properties are change...Assigned
0%
1 Task Description

Andrew,

When we alter about any property of a Hatch entity it seems to be recreated with a newer/higher handle.
This doesn’t influence the drawing order in direct.
But already changing the drawing order of a Hatch it is recreated as a new entity.

It starts to matters in drawing order when there are multiple entities with the same drawing order and that after save/reload. Entities with the same drawing order then receive a new drawing order based on the original but sequentially increasing based on handle.

Because a Hatch is recreated with a newer/higher handle each time a property changes it will thus always end up above the others with the same order even when the original was created earlier.

This is more pronounced when copying/pasting entities from a source to a target drawing.
The original Hatch drawing order is retained but it will always be above existent entities with the same drawing order in the target drawing after save/reload.

Most other entities are probably just updated in situ.
It is unsure to me at this point if merely updating a Hatch is even possible.
And perhaps this is related to the addObject ForceNew flag what is false by default.

Regards,
CVH


	
2539QCAD (main)Bug ReportVery Low(Relative) Polar feet + surveyor notation fails.Assigned
0%
1 Task Description

Andrew,

A user essentially pointed out to an ACAD textbook example.
https://qcad.org/bugtracker/index.php?do=details&task_id=2533
Step 3 of: https://autodesk.blogs.com/between_the_lines/2012/07/drawing-with-surveyors-units-in-autocad.html

Please refer to this topic:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10652

Regards,
CVH

2538QCAD (main)Bug ReportVery LowWeight 2.11 French translation typoAssigned
0%
1 Task Description

Andrew,

When switched to French I detected a typo in the drop down box for Lineweight.

Weight 2.11mm is listed as 1.58mm {2.11m?}
https://github.com/qcad/qcad/blob/master/ts/qcadcore_fr.ts#L1228-L1229
Also see attached image file.


May I ask why only ISO types have a comma instead of a point in French.
The use of a comma is uncommon in the Property Editor even when that is the native decimal separator.
I also detect an extra space between the value and ‘mm’ and that only for the ISO types.

This only occurs in:
https://github.com/qcad/qcad/blob/master/ts/qcadcore_fr.ts https://github.com/qcad/qcad/blob/master/ts/qcadcore_pl.ts https://github.com/qcad/qcad/blob/master/ts/qcadcore_pt.ts


Probably not OS or QCAD version related.

Regards,
CVH

2537QCAD (main)Feature RequestLowMore variants for converting element types could be use...Assigned
0%
Task Description

I don’t actually have any use for this idea currently, but am just posting it here to document it for consideration.

Basically, it occurred to me at least a few more useful conversions between shapes besides the existing ones could be useful.

For example:

  • Converting lines into axially aligned rectangles of a specified “radius” or “diameter” (with an option to delete or keep the original line geometry).
  • An option for the above (lines –> rectangles) that causes the intersections between the resulting rectangles to be automatically removed, like a kind of “automatic/magic wall creation tool” based on laying down lines instead of rectangles and then converting via this tool.
  • Converting circles/ellipses and rectangles back and forth between each other via their bounding volumes. It seems reasonably likely that people will sometimes want to convert circular design elements into rectangular ones and vice versa (e.g. deciding a rectangular column makes more sense than a cylindrical one and vice versa).
  • Converting any arbitrary selection into a corresponding bounding circle (not rectangle, which already exists) of sufficient size to enclose all points in the selection.

Basically, QCAD already has tools for converting shapes with operations that are a natural fit for the existing geometry, but has less tools for converting to entirely different geometry, but such uses could actually still be very useful potentially!

It seems likely to be common enough as a use case to merit inclusion, rather than just using scripting.

I don’t have any pressing need for these and I know that I could script them to create them if I really wanted to.

These are relatively minor ideas. I’m just putting this out here as more ideas for making this already wonderful software even better. :)

2536QCAD (main)SuggestionLowThe little circle that shows the error location when us...Assigned
0%
Task Description

I was having some problems getting some shapes to fill with a solid fill and was frustrated by the awkward numeric coordinate it was giving me for where the error (the disconnected shape points) were, until I fortunately noticed that a tiny pale circle appears around the point where the error is for about just 1 second.

This is a very helpful error indicator circle but is far too easy to miss.

Perhaps making it last longer (or letting the user control that) would be beneficial.

I also wonder if showing multiple such circles (when they exist, as they did in the piece I was working on) at the same time or having that as a UI option would be good.

Anyway, goodnight all!

2535QCAD (main)Feature RequestLowNew tool idea: Scale polyline objects separately, each ...Assigned
0%
Task Description

In my current QCAD file I’m working on, I have a circular hub with a hole in it which I am also trying to place an alternating sequence of rectangular spokes of a certain relative size around.

I had 4 spokes that I had copied and rotated 45 degrees to create 8 spokes in total around the circle. I tried scaling the the non-cardinal spokes relative to the center of the circular ring, but that causes them to also move towards the center of the ring as they shrink, thereby putting them out of place as they scale.

I therefore had to activate the scale tool once per each object and set an origin (focus) point around the area where each spoke is “attached” to the ring in order to stop each from shifting inward to the circle as it scales.

It occurred to me though that there could be a simple tool or option to do this without that.

Each of my rectangles are polyline objects and thus are coherent continuous objects.

A new scaling tool could be designed such that it is based on simply clicking on each scaling origin on each object (using snapping tools if needed) and then clicking a check button (or enter) when done and then causing the scaling GUI to appear so the user can specify the desired scaling. Each scaling would then be applied to where the polylines were clicked instead of to all the objects as one.

This would be a much faster way to rescale a bunch of objects around individually varying relative scaling origins!

2533QCAD (main)Bug ReportLowSurveyor's units never seem to display when selected as...Assigned
0%
Task Description

I've tried several times to try to see what the "surveyor's units" option of the Angular Dimensions format in the UI preferences will display as, but all it ever seems to do is cause the angle measurement to become blank. No angles are displayed whenever this mode is selected.

Indeed, I cannot figure out what the setting actually does besides causing angles to never be displayed.

Is there a way to make this setting do something meaningful or is it just broken?

I found an old forum thread from 2016 about this same issue and it sounds like the same things is still happening since then.

I'm not a surveyor so I have no actual practical use for these units that I can yet see, but I just figured I'd add an report to the bug tracker here in case any developers aren't aware that the bug still seems to exist.

Does the setting do anything besides changing the displayed units in the status bar?

2532QCAD (main)Feature RequestLowAn "auto-tick" or "automated ruler creation" tool (adde...Assigned
0%
Task Description

Hey, this is the first of my feature suggestion submissions that isn’t tied to a corresponding suggestion thread on the QCAD forum.

Should I always create corresponding feature suggestion threads or is it ok (or better?) to just post ideas here?

Anyway though, here’s the idea:

I noticed that it is relatively easy to use things like the QCAD Split Entities and/or Paste Along Entity tool(s) to create an even set of divisions along a curve or line.

There’s also the Misc → Draw → Counter available too, for automated counting.

These together are useful for creating a “scale ruler” to be printed on a schematic for ease of reference or for use in cases where someone forgets to bring along a physical measuring device or when someone else is using that measuring device.

For example, one could print a to-scale 1 foot long ruler (or whatever other scale is relevant, e.g. 1 inch for small objects or just as a nice scale reference/legend/key) on the schematic page for convenience.

However, it would be nice if there was a convenient tool added to the Dimensions tool category that automated this entire process and was able to create arbitrary ruler-like numbered reference scales along lines (and even better if it also worked on arcs, though less important).

Even better would be if this “auto tick” or “auto ruler” tool supported multiple levels of tick scaling (e.g. 2 or 3) such as what one sees on actual rulers.

For example, an imperial ruler for a foot (I’m in the US currently) will typically having increasingly smaller tick marks added at halfway points between each of the numbered points along the ruler’s scale, which makes using it quickly much easier. For example, it’ll have a half-length tick for half an inch and then a quarter-length tick for each quarter of an inch within an inch (with the inch’s ticks being full length).

It seems like it could be relatively easy to implement that kind of nested tick marking system, which would make it super convenient and pleasant for the user of QCAD to create usable to-scale ruler-like objects wherever they desire them with hardly any effort!

I think this idea would also fit extremely well with existing tools in the Dimensions category and would be useful for many/most QCAD users!

It’s yet another good QCAD feature that could attract more people to buy upgraded copies of QCAD in the future I think!

I hope you implement it. Small conveniences still make a big difference.

Anyway, thanks a bunch again for creating this awesome program!

That’s all the suggestions I have for today.

I hope you have a wonderful weekend and upcoming week, etc!

2531QCAD (main)Feature RequestLowAn always-visible hotkey overlay option would be extrem...Assigned
0%
Task Description

Hello! This is perhaps the most useful and valuable of the suggestion ideas I’ve had for QCAD so far!

I think it would be extremely useful if there was an option within the QCAD preferences for making it so that the hotkeys currently bound to each tool button in the UI (if existent) are always displayed such that they are overlaid on top of each of the buttons. There are two main approaches I can think of for doing that (both intended to avoid disturbing the existing layout of the UI):

  1. Display the current hotkey binding associated by drawing it (probably in a distinct color) on one of the edges or corners of each of the buttons (such as the bottom middle side, the lower left corner, or the lower right corner). Even at a small font size I think this would be very effective and useful.
  2. Instead of making the overlaid hotkey display in a small font at a side or corner of each button, you could have the hotkey text be in a large font and overlaid on top of the entire button, using things such as transparency and a distinctive (never used in the other parts of the UI) color to ensure that the button icons is still readable. A broader width of the font stroke may also help if transparency is used, so that the underlying icon lines remain more readable.

Both approaches have pros and cons. I personally lean towards the former, but Husky and CVH seemed to take issue with the readability of small fonts and so I later suggested the later option too.

They seemed opposed to both (at least during the forum discussion). However, I think this UI feature could be one of the best workflow speed improvements for the average user (many/most of whom probably don’t have time to memorize the hotkeys or just don’t end up doing so) of QCAD!

The gains in efficiency and pleasantness could be enormous potentially, even despite it QCAD already being among the most pleasant and well-designed programs I’ve ever used!

It is far faster to be able to instantly read a hotkey from the UI than to have to wait for a tooltip or to look the keystrokes up in the documentation.

Memorization is the fastest of course, but as someone who finds themselves constantly spread thin over many different programs (often half a dozen or more) for long spans of time I often find it difficult to remember all of the hotkeys for each program I use. Having such hotkeys always visible is useful for users who are spread thin, as many people increasingly in the world of software.

CVH suggested that I make custom icons myself, but doing so seems far worse than simply having QCAD automatically read and then print out the corresponding hotkeys over every tool in a programmatic and properly automated way.

I seriously think this would be one of the most awesome improvement you could ever add to QCAD!

Indeed, there is no missing feature I want more than this one!

Few programs do this but the few cases I’ve seen it the feature was extremely useful for speed without having to take weeks/months/years to fully memorize hotkeys only then forget them later. This idea eliminates that problem!

It would be glorious from a usability and accessibility standpoint! Please implement it!

Hopefully Qt’s GUI system is flexible enough to draw overlaid text over the buttons like this without to much hassle. That is the main potential impediment as I see it.

Anyway though, here is the associated forum discussion where I mentioned this idea. It was the same thread as the one where I also suggested adding a way to control tooltip delays.

2530QCAD (main)Feature RequestLowMake it possible to control the tooltip delay time when...Assigned
0%
Task Description

I noticed that every time I move my mouse from the main working canvas (schematic area) to the tool buttons on the left sidebar there is a delay before the first hover tooltip (which displays the tool names and hotkeys corresponding to each tool button) displays.

The tooltips remain fast (near instant) after that initial hover, but it it would be nice if there was an option field for controlling how long the tooltip delay is for that initial display delay.

Currently, on my Windows 10 machine, it takes about 1 full second for the tooltip to show, which may not sound like much but feels like a lot when trying to work faster.

Here is a link to the related forum discussion, which also discussed a different (and I’d say more useful/effective) idea as well.

I’m creating two separate Bugtracker submissions for that one thread though, to keep things clean.

Perhaps I should have created two separate forum thread for that to begin with.

2529QCAD (main)Feature RequestLowAdd normalized unit circle coordinates (complex numbers...Assigned
0%
Task Description

Similarly as for my previous suggestion submission, I also had a related idea for making it easier to work with complex numbers when using QCAD by adding normalized unit circle coordinates as another option in the Angular Dimensions display units options dropdown.

Here’s the corresponding forum thread I started.

Showing tasks 1 - 50 of 519 Page 1 of 111 - 2 - 3 - 4 - 5 - Last >>

Available keyboard shortcuts

Tasklist

Task Details

Task Editing