QCAD Bugtracker

The square symbol offered as symbol in DIM label is the only symbol which doesn’t adopt the layer color.
If I print a drawing in full color it leads to a black symbol in an otherwise colored dimension.

It is also the only symbol which has a solid filling what is confusing when you work with it in Model_Space ...

When I zoom, the text disappears in certain zoom levels after updating to the latest version.

QCAD Professional

Version: 3.25.2.4 (3.25.2.4)
Internet: QCAD.org
Build Date: Nov 18 2020
Revision: 40f4475
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Use TM by mistake to trim a line to a closed shape.
Topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=7780
File included in the topic.
Y1 Original
Y2 Faulty use of TM
Y3 After ‘Undo’

Husky only ‘could agree on a not proper working undo’
The conditional clause of this sentence is ‘the odd choice’.
Blaming this on incompetence.
Insight is the best way to get better ...
... but the rest is more an odd choice of tools for this kind of task ...

Again, the MISTAKE was by accident, not intended, in a flick of the wrist ...
I didn’t change the trimming method, I simply forgot to ... only once.

The ‘undo’ of my incompetent MISTAKE didn’t returned to how the situation was before I erroneous trimmed with TM.
I was simply undoing my erroneous action.

Documented it in 4 quadrants.
For this, 4 times on purpose, and not as a consistent ‘odd choice’.

Regards,
CVH

QCAD Professional
Win installer 32bit
Version: 3.25.2.4 (3.25.2.4)
Internet: QCAD.org
Build Date: Nov 18 2020
Revision: 40f4475
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Most likely not related to the QCAD version, rather an old sore.

File included
Topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=7889#p30803
Confirmed by ‘cccplex’ Linux ‘Latest Ubuntu’

Polyline arcs with Width = 2R render as circle segments rather than circle sectors.
As Non-reversed arcs these don’t explode.
As reversed arc these explode to a single arc rather than a circle sector contour.

There is also still the faulty rendering with Z not zero
https://qcad.org/bugtracker/index.php?do=details&task_id=1923

Regards,
CVH

QCAD Professional
Win installer 32bit
Version: 3.25.2.7 (3.25.2.7)
Internet: QCAD.org
Build Date: Dec 16 2020
Revision: e06f230
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Documented in 3.25.2.4, reproducible under 3.25.2.7
In the attached file:
→ Explode the trial cases and locate NaN Widths.
→ These faulty widths are cleared while saving and reverting.
= work around.

Related Post: https://www.qcad.org/rsforum/viewtopic.php?t=7902#p30902
Related Topic: https://www.qcad.org/rsforum/viewtopic.php?t=7901
Related Commit: https://github.com/qcad/qcad/commit/fcd7929bced7ae328029c1aa2ee2aff2745709c6

Arctic_Eddie reports failing CAM offset at exactly these points !!!
Reported is a faulty arc with radius of over 360,000mm.
- I can not reproduce this under QCAD working further on the Polys with NaNs.
- However the direct offset of such controlpoint Splines is erroneous.
(see file in post 30902)

Arctic_Eddie reports arc radii of over 10,000mm.
- These don’t seem to be faulty.
- I agree that BiArc fitting should be bound to a lower and certainly to an upper limit.
- That should be huge otherwise faint curvature is represented by many
wobbles or too quick by straight lines.
(All this, keeping in mind that QCAD doesn’t return the optimum fitted BiArc, see: https://www.qcad.org/rsforum/viewtopic.php?t=4859)

Regards,
CVH

QCAD Professional
Win installer 32
Version: 3.25.2.7 (3.25.2.7)
Internet: QCAD.org
Build Date: Dec 16 2020
Revision: e06f230
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Discovered in 3.25.2.4, reproducible under 3.25.2.7

Draw any open or closed chain of line entities.
Select All.
OC to Polyline.
Step through vertices.

No example file provided because these NaN values are not saved to a file.
More pronounced with lines as with arcs.
Less pronounced when recombining after an explosion.
Some methods clear these to value = void.
Some methods clear these to zero (OR).
Can also occur when adding segments to an existing polyline with OC.

Regards,
CVH

QCAD Professional
Win installer 32bit
Version: 3.25.2.7 (3.25.2.7)
Internet: QCAD.org
Build Date: Dec 16 2020
Revision: e06f230
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Origin:
I like to start my CAM paths at low curvature instead starting at high curvature.
Ellipses may explode with the startpoint at the tip. (file Y2)

Documented in 3.25.2.4, reproducible under 3.25.2.7

File included with 4 LayerStates
- Original Ellipses: Y1
- Exploded to polylines (32 segments): Y2
- Direct after XP, OR performs different on the left top one: Y3
- Faulty solutions by OR: Y4 (= saved state)

The results may differ with the saved explosions.

With the file.
Y1
TA
XP
Relocate startpoint with OR to an existing reference (called ‘End’)

Regards,
CVH

When placing a hole at x0 y0 there is no G00 x0 y0 in the exported G-Code.
So the first cut was made at the current position of the tool, not at x0 y0!

QCAD Professional
Windows 7, Win installer 32bit
Version: 3.25.2.7 (3.25.2.7)
Internet: QCAD.org
Build Date: Dec 16 2020
Revision: e06f230
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Issues most likely unrelated to OS and installations before 3.25.
Related post:
https://qcad.org/rsforum/viewtopic.php?&t=7982

Flaws documented in full in attached dxf.
The dxf has meaningful Layer States.

4 Columns:
- Prior Art
- The test cases
- Actual results
- Results with proposed fix

Tried as many things as I can come up with.
Orange: Flaws
Red: Errors
Green: Good results (or as good as I can get them)

Solution(s) given in attached script explode.js
(I am just a simple guy and wouldn’t know how to file a pull request on GitHub ......)

In section: “explode polyline into line and arc segments”
group: “if (RPolyline.hasProxy() && polyline.hasWidths()) {....}”
All additions, updates & typos are marked with “CVH”, one can textual search for it.
Over-documented for sure.
Any Eaction is to debug in Windows and is obsolete.

Included PreferencesPage.ui is updated for the all Splines from Text fix
Still in consideration: Forcing cubic splines from text to degree 2 ...
... I am rather convinced ...

CVH

In the Application Preferences>Draw>Text dialog, when first opened, the Uncheck all and Check all buttons are not disabled if the Show font preview in font controls check box is checked. If you click on the Use reduced selection of fonts check box twice the buttons become disabled.

QCAD Professional
Windows 7; Win installer 32 bit
Version: 3.25.2.7 (3.25.2.7)
Internet: QCAD.org
Build Date: Dec 16 2020
Revision: e06f230
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

Forum Topic: https://qcad.org/rsforum/viewtopic.php?t=7988
File included.
I have no intention to make 48 separate reports.

CVH

QCAD Pro 3.25.2.7 Win7 Wininstaller 32bit
Related Topic:
https://www.qcad.org/rsforum/viewtopic.php?&t=7954

Reported is that black is saved as #00004c (dark blue)
Radek (iMac (Retina 5K, 27-inch, 2017), Catalina 10.15.7 (19H114)

My system/installation saves black as #4c000 (dark red)

When using single primary colors these get reduced to #4c, #7f, #99, #cc & #ff.
The threshold for that are #00, #65, #8b, #b2 & #e5
See: DimColorScale (png & dxf)

8 standard CAD colors fail saving correct
Black (something with #4c)
Dark Red, Dark Green, Dark Blue, Dark Cyan, Dark Magenta, Dark Yellow
(#80 turns #7f)
& Gray
(#adadad instead of #a0a0a4)

As with Gray, when mixing the 3 colors it gets rather fuzzy ...
#505050 & #555555 both turn #5b5b5b
&
#464646 turns #4c4226

A snippet of my investigation is included in the topic
(45 files in a ZIP)

CVH

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)

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,

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,

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,

Found a bug in the 3D Simulator execution

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

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 there,

A friendly request to add the option to set a maximum lineweight for raster conversions via dwg2bmp.

Depending on the LW configuration of the CAD file, rasterization operations sometimes yield terrible results (see attachment). This would also mirror the similar “-min-lineweight” options available on “dwg2svg” and “dwg2pdf” (although not on “dwg2bmp”).

See also: https://qcad.org/rsforum/viewtopic.php?f=32&t=6298

Thanks!

Hi!

A friendly request to add an option to disable hatch rendering on “dwg2bmp” conversions.

Depending on the nature of the conversion and the density of the hatch, this may render unintelligible images (see attachments). The option could look like “-t, -nohatch” to indicate hatches should be hidden before rendering. This could potentially become an option too for “dwg2svg” or “dwg2pdf.”

Amazing product, thank you so much!

It would be nice if QCAD spit some kind of warning message when trying to render a layer with a name that doesn’t exist (and perhaps render nothing), rather than silently rendering an empty image. :D

See https://qcad.org/rsforum/viewtopic.php?f=33&t=6453

Add a command line switch to dwg2pdf to export a given block instead of “*Model_Space”.

Add support to specify multiple blocks (layouts) to output (one per page).

When trying to plot a dwg or a dxf to pdf where the viewport is orientated to a different angle than north up
the data in the view port is plotted north up.
see attached DWG and pdf for clarification.

We currently have a paper-space using two viewports with different layers from the model-space frozen. Unfortunately in the pdf output the layers which are frozen show up.
dwg2pdf should obey the specific frozen layer for each viewport

Implement a command line switch to only show a list of given layers for dwg2* command line tools.

Add parameters to the function DL_Dxf::writeVPort.
This way users will be able to specify the desired viewport.

Is the github the official repository? Are pull requests sent there accepted?

QGroupBox widgets with <property name=”checkable”> are not saved in Qcad3.conf

implement

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

Insert field into drawing that displays current date, file name, ...

Modify - Round - Click polyline - round all corners

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

A missing feature in my work are logical operations (combine, intersect, ..) for polylines

Example:
Draw some elements, select them, say combine. The result will be the outline of all elements.

For and behalf of mandrena

To add another Arc tool option in Arc tools set:

1.Specify Start point for Arc.
2.Specify End point for Arc.
3.Specify “Tangent” direction (without being restricted in input field) so you can visually select a point on your desired Tangent line!

it would be ideal to be able to have the option to autohide the side panel to increase the visible drawing space when working on a small screen.

Points on line: enter distance instead of number of points as a variant of the tool or as a new tool.

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

The modify stretch tool wants first and second corner, start and end point, then starts afresh. When I turn on restrict horizontally eg to align two points between start and end, the restriction sticks and I have to call restrict none, to be able to perform the next iteration, set the first corner then.

So, in the quest for a comfortable user interface, it was nice, if the modify stretch first/second corners parameter setting was not affected by current restrict/ortho etc. settings. Actually, that does not make any sense at all anyways, does it, a rectangle is defined by two degrees of freedom, isnt it?

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

To add the option to ‘print only’ selected area in a drawing.

See:
http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1867

Apparently this was possible in QCAD 2 due to the default behavior of Qt.

Hi,

in QCAD3 RC2 points were printed as crosses, in QCAD3 RC4 they are printed as (very little) points. I think this isn’t a bug but a feature.

It would be nice if one could change this behaviour / select the symbol of points.

Best regards - Stefan

This is a double post of http://www.ribbonsoft.com/rsforum/viewtopic.php?p=5870#5870 as suggested there.

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 )) ?