QCAD Bugtracker

Status Bar menu remains unchecked even it is toggled on or off

Hi,

I am using mac version and I have annoying issue with trackpad.
I use qcad primary with my trackpad and under application preferences (Graphics View/Navigation), my setting is as follows.
Mouse wheel / two finger swipe: Scroll (Trackpad...
Enable pan gesture : unticked (found that enabling this often goes into pan mode when I am just moving my pointer around)
Limit zoom and scroll to prevent overflows : ticked (hoping that this would prevent weird zooming issue. I will describe what I am experiencing later this page)
Reverse mouse wheel direction for zoom :unticked
Mouse wheel zoom factor: 1.02

Things work as expected:

• panning with two finger swipe

• and the rest

Issue I am experiencing:

Often, when I am zooming in and out with two finger gestures, the view suddenly sets to some weird state and my drawing goes off the ruler.
The mouse point remains where it is.

Workaround:
Reset viewpoint with autozoom and navigate around.

Expected zoom behaviour:
I expect viewpoint to zoom in / out at where my mouse pointer is or at least the centre of current view point.

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

See:
https://qcad.org/rsforum/viewtopic.php?&t=6827&p=25992#p25992

Offsetting 32 polys from ellipses fails.
Offsetting 16 polys can be completed with 2 selections for outer and 2 for inner.

For some reason the offset function halts premature.

Regards,
CVH

When I’m drawing inside a layout block the offset tool picks up lines from blocks that are hidden.
It is not happening with all the block.

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

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

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

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.

Hi Andrew

In QcadCAM when using the new Themes or User Created Themes the Layer and Block Tabs Appear to be reversed in East and West Positions.
I have discussed this with forum user PeteVick and he cannot reproduce this behavior in Qcad Pro... he suggested submitting this bug report.
I didn’t notice this until he pointed it out and don’t expect it to be high on your list of things to do..

Best Regards
John Hyslop
PS We are both using Linux Mint 20.1 (64bit) which is based on Ubuntu

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

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

Windows 7 pro 32 bit msi-Installer
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

Andrew,

In the attached dxf:
Besides that it is clear that duplicate vectors are not filtered ...
Where a segment is crossing in another node a non valid node is returned as self-intersection point.
Seems to be unrelated to CW/CCW or tolerance.

Where 2 nodes coexists 4 duplicate vectors are returned.

Regards,
CVH

The tool “Clip to rectangle” / “Cut at Area Boundary” tool used on an area with lines and arcs will partly complete arcs to circles.

How to reproduce the bug:
1-open a new file
2-select text tool, simple text(one line,no formatting) and alignment in base-left
3-write some text in somewhere position in the draw, repeat this in others positions
4-save the file in .dxf R15 [2000/LT2000] (dxflib) format
5-close Qcad
6-open the saved file, the writhed text lose original position and now all the text have 0,0 position

Post processor “LaserGBRL (offset) [mm] fails to turn off/on (M5, M4) at Tabs.

Forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=85&t=9552&p=38496#p38495

Andrew,

I can’t find any documentation concerning OffsetBothSides under Misc .. Modify.
It is not listed in the QCAD features nor in the changelog.

There was a Feature Request FS#1130 for this, I think you might want to close that as being implemented.

The tool asks for a Line, Arc, Circle, Ellipse, Spline or Polyline.
It also seems to act on shapes that can be exploded to such entities like Text, Dimension and Hatch entities.

There may be many ‘Result loop not closed’ or ‘No offsets possible’ warnings when hovering over entities on a drawing.
The preview may be partially, one or two sided and even two sided partially and closed with semi-circles.

I only successfully created a dual offset for open Splines, open or logically open Polylines.
All other attempts result in a single offset at the indicated side.

There are the usual exceptions for Polylines with arc-segments but that is related to small arc segments and being tangentially connected.
Only tested it on a Win7 platform.
I don’t suspect that version 3.27.8 includes a fix for that ...

Regards,
CVH

Andrew,

Most probably not related to OS or QCAD version.

When hatching an area with Hatch from Segments (HS) there might be false positive warnings on open loops.
It seems that this is related to the orientation of the indicated segments and the order of selection.
The real problematic position is not always the first that is reported.
Loop count is increased even if it is a single loop.

Included a basic test drawing to replicate these.
Further details to replicate the issue are in the file.

Regards,
CVH

Andrew,
For more detailed description please refer to:
https://www.qcad.org/rsforum/viewtopic.php?f=33&p=40081#p40081

In the included screen grab below, left is when drawn cubic, closed periodic, from 4 points.
Right is when the file is re-loaded.

It is hard to select the incorrect shape when pointing near it ... Probably it is referring to the correct internal shape.
After drawing it explodes to a Null length polyline with 2 identical vertices.

I can’t include the error in a file as it reverts on re-load.

The same issue exist for quadratic, closed periodic, from 3 points.

Regards,
CVH

Andrew,

Referring to this forum post:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10152

With radii 1341.35667735 and 26 the relative tolerance is 0.00683678 and exceeds the former used fixed tolerance of 1e-4.

These arcs will then be considered to be tangent and the intersection point is 0.31024 units to the left of where we expect it.

Implemented: https://github.com/qcad/qcad/commit/77ae3e4518cc34f178779d2d2c724adcf80c229d#diff-dcc4e31eaeaed5a047f65dbce4ddda4bcd4d604e9e1005ee8481ded273768449

Updated: https://github.com/qcad/qcad/commit/071b60acd1176e6301bf6b6fcf716684221a97e8#diff-dcc4e31eaeaed5a047f65dbce4ddda4bcd4d604e9e1005ee8481ded273768449

I had already expressed my reserves on the relative tolerance but that was already a better solution for small arcs:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8775&p=34907#p34907

We could limit the tolerance by:
A- The smallest of the fixed and the relative.
B- A relative tolerance based on R2 there circle 1 is forced to be the larger one.

This will never account for the position in the plane.
At a certain point the tolerance will be less than the accuracy/certainty of the values.

Regards,
CVH

Andrew,

It took me a while to find the source of a certain freak bug I encountered.
I used the RLine.isParallel(RLine) as a test for knowing if line segments were parallel or not.

Included below is script code that mimics the functionally of isParallel().

As far as I know isParallel() is nowhere used in the QCAD open source.
Textual only found in RLine.cpp & .h or under: opennurbs, ecmaapi\generated and ecmagenerator\src.

// Example:
// RShape1: RLine(RShape(address: "0xcd70e28"), startPoint: "RVector(969.219858, -171.914894, 0.000000, 1)", endPoint: "RVector(1010.000000, -140.000000, 0.000000, 1)")
// RShape2: RLine(RShape(address: "0x7659770"), startPoint: "RVector(969.219858, -171.914894, 0.000000, 1)", endPoint: "RVector(930.000000, -340.000000, 0.000000, 1)")
----
var aShape1Angle = shape1.getAngle();    // =0.6640461628266838 rad
var aShape2Angle = shape2.getAngle();    // =4.483157047107694 rad
----
// RLine::isParallel(RLine) -> aTest1 || aTest2
var aTest1 = RMath.isSameDirection(aShape1Angle, aShape2Angle);              // =false
var aTest2 = RMath.isSameDirection(aShape1Angle, aShape2Angle + Math.PI);    // =true
var aTestOr = aTest1 || aTest2;                                              // =>TRUE !?
----
// # BUG # RShape1 is considered as parallel with RShape2
----
// RMath::isSameDirection(dir1, dir2, tol) ... tol = RS.AngleTolerance = 1e-9
// for aTest1 -> ax1Test1 || ax1Test2
var ax1Dif = Math.abs(aShape1Angle - aShape2Angle);    // =3.8191108842810104 rad
var ax1Test1 = ax1Dif < 1e-9;                          // =false
var ax1Test2 = ax1Dif > 2*Math.PI - 1e-9;              // =false
var ax1TestOr = ax1Test1 || ax1Test2;                  // =>FALSE
----
// for aTest2 -> ax2Test1 || ax2Test2
var ax2Dif = Math.abs(aShape1Angle - (aShape2Angle + Math.PI));    // =6.9607035378708035 rad
var ax2Test1 = ax2Dif < 1e-9;                                      // =false
var ax2Test2 = ax2Dif > 2*Math.PI - 1e-9;                          // =true
var ax1TestOr = ax1Test1 || ax1Test2;                              // =>TRUE
----
// # BUG # The second test of the second isSameDirection() test returns true because ax2Dif is over 2pi

Regards,
CVH

Andrew,

See attachment with example:

Solution included on layer ‘Solution’.

Regards,
CVH

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

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

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.

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

Text dialog (QTextEdit) strips tabs in toHtml.
If tabs can be retained, text entities could support tabs.

Hi,

As a typical command line draftsman (still using acad10 for dos, since microsoft doesn’t supoort Win NT anymore),
I noticed a severe lack on command line acces in QCAD.

For example I find the icon and pixel selecting methods within qcad very confusing and rude.

With the normal cad Select command I can select exactly what en how I want it.

I intend not to be rude, but I find my drawing screen littered all over with all kind of very specialist menu’s,
tools and options. Sorry, I just want to make a drawing at the natural intuitive way, as with a pencil.
So I use command line Commands, such as Move, Copy, Change, Select, a.s.o.
For a ‘Command scripting’ user (-batching is a different tool!-),
it seems to me logical these basic commands should be accessable.

I love using the context menu, speeding up my workflow indeed.

I would like to suggest that we have the added option to show only icons if desired and also that maybe an option to save and show commonly used tools!

Maybe the context menu could be configurable to show two columns, one for the normal last used tools and the othjer one for the user saved tools?

What do you think?

The line for “General properties”, “Layer” the line is too narrow,
so you do not see the layer name when the Property Editor is pinned to the side.
(see Forum - Suggestions and Feedback):
https://www.qcad.org/rsforum/viewtopic.php?f=31&t=5239

Make unprintable layers also hidden in print preview

When selecting multiple blocks that contain the same attribute names, attribute properties appear with the values of the last selected block instead of “various”. I do not know if this is a “bug” or developer option, but “various” would be better in my opinion.

Module mise à plat d’un cone

Bonjour,

Serait il possible dans un futur d’ajouter un module de mise en plan de cone.

Une petite fenêtre sur lequel on donne par exemple :
1- Ø haut
2- angle de coupe du haut
3- hauteur du cône
4- Ø bas
5- angle du bas
6- épaisseur matière

Ce qui permettrai de sortir une mise en plan a plat de la forme

To reproduce

Actual

Expected

Motivation

Workaround

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.

Text and/or DIM used in blocks will be mirrored if inserted with a vertical/horizontal flip option.

Text/DIM which was successfully used in previos QCAD versions are now mirrored if they are loaded in the current version.

Version 3.23.0 doesn’t shows this behavior.

https://www.qcad.org/rsforum/viewtopic.php?f=32&t=7206

As it can be seen in the attached image, QCAD toolbars may dock to a position slightly outside the visible area of the screen. After having docked there, I have not been able to move them any more. Their current position is just in the middle of the screen.

The position of the toolbars remains the same after the deinstallation of QCAD, shutting down, restarting the computer and reinstalling QCAD. I kindly ask for help.

Kind regards
Reinhard

no task description

1) Line with command prompt in Command Line widget is missing padding/margin - letter C is glued to frame.
2) In the “Selection Filter” widget there is an “whitespace” character before colon “:” symbol on multiple places, it doesn’t seem repeat anywhere else

e.g: If I use content out of the clipboard to insert it multiple times into the drawing with using the Middle Manual snap [SN] the snap can’t be locked [SQ] and I have to reactivated the snap again and again for every following insert.
Other snaps like END or CENTER work flawless in this scenario.

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!

Reason: Same underlined keys are used for different menus

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

Andrew,

At present QCAD/CAM the tool drop-down box displays tool number and diameter between brackets.

It would be more appropriate to display if it is a mill or a drill and/or the description of such.
In a further stage of development ball-nose ... Conical ... And so on.

I have several specialized mills with the same diameter.
End-mills, roughing mills, routing mills, face mills ....

Tools 1(ø6mm) or 2(ø6mm) don’t say much if tool 1 is a side-mill and tool 2 is a high speed drill for metal.

Related forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10722

Regards,
CVH

Andrew,

I know that GCodeMM.js and GCodeIN.js are generic postprocessors.
Mostly used as base for other or custom postprocessor.

The distinct nature is pretty clear from the filename and the suffix in the display name.
Another distinct nature is that they include this.unit = RS.Millimeter / RS.Inch intended for the CAM side.

Why don’t they include at least a G20/21 in a generic header?

There are several more specific postprocessors where I miss these G-codes for the measurement system.

True, if they are not supported, no error messages would occur when omitted.
The danger is that users rely on build in postprocessors hoping that it matches with the default measurement system of their setup.

IMHO it is safer to trigger an instruction fault before attempting to execute a wrong motion.
As fail-save as possible should always be the goal.

Regards,
CVH