QCAD Bugtracker

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

Win7pro 32bit Wininstaller Qcadpro 3.23.0

Draw an arc.
Select the arc.
In Property Editor:
Set start angle to 135
Set end angle to 135

SweepAngle = */-360

edit the end angle and add “+360”, hit enter

SweepAngle = 0

An arc with zero sweep is a point.
A point is not an arc.
With the same start and end parameter an arc should have a sweep of +/-360.
As for entries by points or by angles.

Regards

Just starting with QCAD, for some hours now - really excellent user interface (compared to other low budget CADs, like DCAD, or BeckerCAD...) !

Surprisingly, point coordinates - entered via the command line, and shown with correct positions on the drawing- are not displayed correctly with the ‘dimordinate’ (DO) command.
There are no negative values, even when the center point (0;0) is right in the middle of the drawing, so points left and below should have !

GW.G

Some functions / methods can generate some sort off entity or part with NaN / Null / Null-lenght ... props.
Some explicitly don’t and test their actions with isNull().

As these serve a purpose in some processes, trails of them can be part of the results.
For some users Null / Null-lenght are meaningfull, for other users these produce errors down the line.
In a few cases its a desirable feature eg. controlpoint spline.
(Allthough there are no Null props involved with equal successively controlpoints)

Many problem post on the forum are related to Null - Zero and so on.

In some cases it can’t be undone by re-editing the drawing.
https://qcad.org/bugtracker/index.php?do=details&task_id=1925

If it can’t be undone by Undo/Redo it is a bug.
https://qcad.org/bugtracker/index.php?do=details&task_id=1757

In some cases there is a difference noticed after file save-close-open.

Hi,

my setting for “Auto Zoom on load” is checked to on. That works perfect for me for most of my drawings.

But if I save a drawing with Layout Viewports then I have to adjust every Viewport again after loading.

Would it be possible to have an option below Application Preferences / Graphics View / Appearance / Auto Zoom on load / ON which excludes drawings saved with Layout Viewports?

In the Advance SVG Export dialog, when I edit the filename to be different than the default file that already exists and then clear the checkbox for “Overwrite existing file without asking” just to make sure that I haven’t already created a file with the modified name as well, then I get a popup warning that the export would overwrite the default filename, not the name as edited. In other words, the overwrite check ignored the fact that I edited the filename.

Observed on MacOS Mojave (10.14), but probably applies to all.

Diametric text is always placed above a horizontal measurement.

I often want to indicate both the inside and outside diameter of an object e.g. a wheel using diametric text. The text is overlaid and illegible.

To avoid text overlapping, I use Horizontal Aligned because I can control the position of the text to avoid illegible text.

A better method would be to alternate the placement of diametric text (alternatively) above and below a measurement so that in the majority of cases an overlap would be avoided.

Similarly for a vertical measurement, the text is overlaid and illegible.

When the angle is almost vertical, the angle controls the side the text appears however it also reverses the direction of the text (which is logical but not attractive).

Kind regards
Simon

The attached file is not saving font preference.
All fonts on the online layer are reported as the standard font. If I highlight one or all of the text entities and change the font to something like Yu gothic light, the property page reports yu gothic light and the screen reflects the changed font.
If I save, close and reload, the fonts for all text is again “standard”.

So then I try to enter new text via the “A” draw text command icon. I select “Broadway.ttf” as the main font in the text entry dialog.
One word “Broadway” is entered as the text. it appears on the upper left of the screen as expected and the font name is Broadway in the property editor. If I look at the dxf file source there is a whole bunch of text styles.
I save and close the file, and then open it again. Now the word Broadway has changed to font name “standard” in the property editor and is very definitely not the Broadway.ttf font.

I am not the originator of the file, I am just trying to change the font. If I start a new file and enter new text the font saves just fine, so I am thinking it is a setting somewhere, but I am unable to find it.

We (me and my customers) use these files for engraving so exact font is critical.

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

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.

See:
https://www.qcad.org/rsforum/viewtopic.php?t=6650

Hi,

It would be less confusing to read messages in the command line protocol if it would use the same coordinate separators like the settings below Application Preferences / General / Coordinate Format.

This example shows the “Absolute Cartesian Coordinate” but of course all corresponding format settings should be used within messages.

Absolute Cartesian Coordinate: Setting = semicolon (;) but the message will use division (/).

To measure in the format DIN 1356 , Architect
It is hard work to do this manual input with meta characters.

This is a trim method I am missing in Qcad.

20 years ago it existed in CadKey.
You had a bunch of lines or segments.
You defined a (new) line or segment as cutter.
‘Trim All’.
You pointed at the side of the cutter entity to trim all intersecting at that side.

Pritty the same as in this topic:
https://qcad.org/rsforum/viewtopic.php?t=5221

Only in rare cases I can use Husky’s workaround as pro.
It all depends on what else is in the clipping rectangle that is needed to trim all intended.
If of no use all single crossing entities have to be chosen one by one.

Regards,
CVH

When working with multiple Viewports with different scale it could be very useful to have extra properties controlling how dimensions are rendered in the viewport:

1)
E.g an extra “Dimension Scale” under “Scale” in the Viewport selection’s ‘Specific Properties’ section, could allow having the same size when printed.
This Dimension Scale would be multiplied on top of the Scale value, but only for Dimensions rendering.

2)
Toggle button for hiding any dimensions in the Viewport. Maybe this should be controlled by being able to specify a Layer that should be hidden in this Viewport only, then I could select my Dimensions layer here.

The Viewport properties:
https://i.imgur.com/s07JtaB.png

Draw an ellipse, select it, draw an hatch of type gravel: it doesn’t appear at all.

Only for gravel.

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 find it hard to select the correct tool by a small bug

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

When I create a simple drawing, I cannot export the gcode until I restart qcad.

general steps to reproduce the issue:
1. open a new drawing
2. Add a letter “D” near the origin in Arial font, about 7mm tall.
3. explode it
4. save the drawing
5. Fill in in the “cam configuration” 6. Select the drawing and generate the tool paths.
7. Hit the “export button” or the menu item.
8. Observe that you see the “camexport” command appears in the command section, but there is no file generated for the gcode.

If you restart qcad, then the gcode will export as expected. Also, it appears to work for more complicated drawings. I had the same issue, when I tried to generate the same thing, but using the string “November 2019” at 5mm height. I am using up to date MX Linux with kernel version 4.19.0. I also observed this behavior under Windows 10 professional.

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!