QCAD Bugtracker

Looks like error, but may be that’s feature request.

CAD software uses typical navigation behavior as:
Wheel = Zoom; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right.

Any other software like browsers, office software (openoffice writer, ms excel and so on), 2d paint software like GIMP (Photoshop and so on) uses other behavior:
Wheel = Scroll up/down; Ctrl+Wheel = Zoom; Shift+Wheel = Scroll left/right.

Users, that intensively use CAD and other software simultaneously prefer to make same behavior in their applications switching CAD scroll to plain mouse wheel.

QCAD’s “Application Preferences”: “Graphics View: Navigation”: “Mouse wheel/ two finger swipe”: “Scroll” allow user to assign scroll up/down to wheel mouse instead of Zoom. But there is mistake Ctrl+Wheel didn’t change to Zoom. Ctrl+Wheel continues to scroll up/down, as the wheel.
Wheel = Scroll up/down; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right. No zoom!

Draw manipulation at this mode like a hell: you need to use wheel in conjunction with Ctrl/Shift to point draw in desired position, than move your hand to +(-) for make desired zoom.

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

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

Not related to OS, nor version.

The method Polyline from Segments (OC) can be configured for tolerance and simplification in the Options Toolbar.
The method Polyline from Selection (OG) has no UI or none showing.

OG retrieves a tolerance from QCAD.ini, what is initially not set:

    var tolerance = RSettings.getDoubleValue("PolylineFromSelection/Tolerance", 0.001);

The tolerance will be default = 0.001 similar as the default in AppPrefs.
The tolerance setting is included in QCAD.ini after changing the AppPrefs entry.

OG calls PolylineFromSelection.autoJoinSegments with this tolerance:

    var counter = PolylineFromSelection.autoJoinSegments(di, tolerance, this);

PolylineFromSelection.autoJoinSegments calls PolylineFromSegments.createPolylineShape
with simplification hard coded to true. (last parameter)

    // create polyline from line, arc, spline or open polyline entity:
    var polyline = PolylineFromSegments.createPolylineShape(
                    entity, doc, vTolerance, op, undefined,
                    traversed, callBacks, undefined, true);

I would like to see the simplification optional and default = true.

Regards,
CVH

Unrelated to OS, nor version

Reported Jun 23, 2020 in: https://qcad.org/rsforum/viewtopic.php?f=30&t=7372

Status Dec 24, 2020: https://qcad.org/rsforum/viewtopic.php?f=30&t=7372#p30955 Documentation is updated.
The Classes still refer to an ‘angleTolerance’.

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

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

Select the previously selected entities.

The option for vertically and diagonally stacked fractions would be helpful for both the text creation tool and as the output of dimensions.

An option for unidirectional dimensions, in addition to the default aligned dimensions.

Add functions to the Reorder tool, similar to the functions of the counter tool, undo last step and start at any number, allowing corrections and restarting the tool part way through.

See the discussions at https://qcad.org/rsforum/viewtopic.php?f=32&t=8170

The “Define annge using mouse cursor” of the Rotate tool would be useful in the Move and Rotate Tool

When saving a view, it would be great if the view also saved which block (model space, layout block, or any other block) that was active at the time the view was saved and when the view is later re-activated, the corresponding block would re-activate.

Case:
Drawing with text, zoom in and out with one of the common methods, text will disappear in certain zoom level

Same drawing zoomed in and out in 3.20.0.0 doesn’t show this effect - works just fine.

When I modify partly a DIM with “Stretch” or changing one Extension line position with drag and drop the Value text is updated which is nice working. Unfortunately the previous value stays in place and is overwritten by the actual value. I think for a good readability the previous value should disappear in the moment when the new value is presented.

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

Angle Display is decimal although the decimal display is disabled in Application Preferences.

Format should be 17° 31’ 52” instead of 17.531111.

It would be a very interesting feature to add to future versions.

I also use AutoCAD Mechanical 2012 and the BOM is synced with every balloon on the drawing. Making it easy to edit.

The core BOM accepts formula fields and we can easily calculate the mass of a part, with some Ifs and math.

The BOM that is shown in the actual drawing is more simplistic, and has just Part number, Quantity, Mass and the Description. But it’s related to the “core BOM”.

It’s a very interesting thing! It would be great on QCad.

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

QCAD Professional
Windows7 pro WinInstaller
Version: 3.26.4.5 (3.26.4.5)
Internet: QCAD.org
Build Date: Jul 20 2021
Revision: e596276
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

In the example given by ‘turtle’ .. why_is_this_not_closed-v2.dxf
https://www.qcad.org/rsforum/viewtopic.php?f=32&p=34157#p34153

Selecting hatch boundary segments of the horizontal polyline segment at
(1169.933593;274.432562)-(1089.933593;274.432562)

Segment selection stops where the AR-CONC hatch pattern touches the horizontal segment.
Such intersections points where already no longer regarded as snappoints.
See :
 FS#2090 : https://www.qcad.org/bugtracker/index.php?do=details&task_id=2090.
Related topic https://www.qcad.org/rsforum/viewtopic.php?&t=7340&p=28414#p28414

Regards,
CVH

no task description

I am getting random crashing on my MacBook M1 chipset while using QCAD Pro. There is nothing in particular that you can do to replicate as the crashing is completely inconsistent. Have had it crash when pressing escape while using measurement tool, but have also had it crash while using the app and selecting a tool.

Included crash report, which has also been sent to Apple.

Thanks

In the US, it is (unfortunately) still common to use US survey foot. It seems at least some DXF applications/libraries support this unit as a $INSUNITS value, some references:

• https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2020/ENU/AutoCAD-Core/files/GUID-A58A87BB-482B-4042-A00A-EEF55A2B4FD8-htm.html
• https://ezdxf.readthedocs.io/en/stable/concepts/units.html#insunits

There are two issues regarding this with QCAD:

1. If you open a document with $INSUNITS being 21, it’s reset to 0 (unitless/unspecified) when saved again, even when not changing anything.
2. It is not possible to select these units in the GUI.

I don’t know about standardization of these values, but my hope is that it’s at least possible to preserve the unit in an existing drawing. Given that this unit is supposed to be obsolete in some years, it might seem less important, but due to this transition, it might get even more important to be able to distinguish between units. Thanks!

As a heavy mechanical drawings user, it would help a lot to have an option to exit a block saving as a new name and making it a new entity from that time ahead.

Example: if a have a lot of screws, one of then is behind another peace and need the to have some lines changed to hidden style lines, in the flow of the work is great if I edit that screw in place and when exiting have the option to save as a new block, to don’t mess with other entities of the same block that I don’t want to change. Yes, there is a workaround that is duplicate and rename the block prior to the editing, but a save as seems to work easier.

Thanks Andrew and team!

I have set the grid/snap value to X=.0625 Y=.0625 on all 4 viewports.
When zooming in and out the grid/snap scale changes from .0625 to 3.90625. at this point the grid/snap points differ,
This causes a variation in the grid/snap reference points lending to drawing errors.

example
When I use the grid settings defaults .01, when zooming in and out, the grid/snap scaling doesn’t seem to have this issue.
Other values do, See below.

set value first zoom second zoom next zoom

	point		point		point ...	

0.01 0.1 1.0 10.0 ...
0.02 0.04 0.4 4.0 ...
0.04 0.16 1.6 16.0 ...
0.05 0.25 2.5 25.0 ...
0.0625 0.390625 3.90625 39.0625 ...
0.0254 0.64516 6.4516 64.516 ...

Why is there a squaring of the original set value? Which then becomes a new zoomed grid/snap value?

QCAD Professional
Version: 3.26.4.0 (3.26.4)
Internet: QCAD.org
Build Date: Jun 3 2021
Revision: 0bb4334
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

The option of a layer state widget would be a nice way to see and select between different layer states.

When using the vertical line tool, you can enter a length value in the options toolbar, then place the line. If you want to change the length, you just need to enter a new value and the length field will update. However, there seem to be cases where after 10-20 entries, the focus goes off the length field in the options toolbar, requiring the user to bring focus back to continue. I could not seem to duplicate this behavior with the horizontal line tool.

Hi Andrew,

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

Attached a laser tool proposal

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

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

Hi Andrew,

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

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

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

Hi Andrew

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

Hi Andrew

A request for adding some fields to the toolpath

Hi Andrew,

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

Recreating the same error however is possible

Hallo Andrew,

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

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

Hallo Andrew,

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

Example added as pdf.

Greetings

Hallo Andrew,

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

Hallo Andrew

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

Hallo Andrew,

testing the drill toolpath I used single point markers.

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

Cam Export and generated G-code is not effected.

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

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

Hallo Andrew,

I have revised the PWM Post Processor to Revision D.

Hallo Andrew,

Found a bug in the 3D Simulator execution

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

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

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

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

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

Regards,
CVH

Hello dear CAM developers!

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

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

Many thanks
Best regards.

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

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!

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