All Projects

IDProjectCategoryTask TypeSeveritySummaryStatusOpened by
 1758 QCAD BugtrackerQCAD (main)Bug ReportHigh Draw > Polyline > Create from Selected Entities: crash  ...ClosedCVH Task Description

(Re-)combining polys touching at node with ‘create from selected’ leads to application crash.

QCAD 3.20.1 Win7 32bit

In the file example 2.

 1747 QCAD BugtrackerQCAD (main)Bug ReportMedium Scaling w 2 ratios fails to scale polyline arc ClosedCVH Task Description

Scaling without keeping the aspect ratio fails to scale an arc to an ellips when this is part of a polyline.

Discovered while documenting feature request ‘Skewing’


 1750 QCAD BugtrackerQCAD (main)Bug ReportMedium trimming polylines ClosedCVH Task Description

Trimming polylines especialy those with a string of small segments should be done at the intersection of those polylines.
Now trimming is done with the seggments that where the nearest when selecting the two polylines.

 1604 QCAD BugtrackerQCAD (main)Bug ReportLow  Exploding splines has equal results disregarding the s ...ClosedCVH Task Description

The explode function preference ‘Spline Segments’ has no influence on the created number of polyline segments any more.

Attached is a file with an example.
The same spline exploded with setting 2-4-8 & 128 segments.
Result for the indicated spline is 59 and constant.

 1605 QCAD BugtrackerQCAD (main)Bug ReportLow Edit > Paste: Empty layers created when pasting to curr ...Closed1CVH Task Description

Copy - Paste to current layer from an other drawing creates empty layers, where the entities orininated from, in the drawing where they are pasted to.

 1606 QCAD BugtrackerQCAD (main)Performance IssueLow Selecting 'Draw Order' halts system temporary ClosedCVH Task Description

Merely clicking on ‘Draw Order’, and usualy unintended, halts the system for several seconds up to several tens of seconds.

Intel(R) Core(TM) i7-2600K CPU @ 3.40Ghz
4,00 GB RAM installed 3,49 GB usable
32-bit Operating System
Windows 7 Professional SP1

 1637 QCAD BugtrackerQCAD (main)Bug ReportLow Buttons Layer List Widget acting on other open file  Closed1CVH Task Description

With multiple files open 4 of the 5 buttons of the Layer List Widget are acting on an other file that is open instead of acting on the file in focus.
in this condition only Add Layer YA acts on the file in focus.

Not easy to reproduce.
Encountered it more frequent
after copy with ref and pasting.
with more then 2 files open.
with similar drawing file names.
Did reproduce after several hopping between files.
Usually acts on the first open file but this can be different as in the example.

workarround none; save all; close all; close Qcad; reopen and redo.

 1638 QCAD BugtrackerQCAD (main)Bug ReportLow SansNS.cxf coding mismatch ClosedCVH Task Description

Some 50 glyphs in SansNS.cxf start with [#.... instead of [....
These glyphs are replaced by a ? when used.
Merely removing the # fixes this.
Corrected file included.

 1648 QCAD BugtrackerQCAD (main)Feature RequestLow Uniform Layer listing in dropdown as in Layer List Widg ...Closed1CVH Task Description

The order layers are listed in dropdown boxes is different as how there are presented in the Layer List Widget.
Uniformity can shorten lookup time drastically with a large number of layers / sublayers.

 1708 QCAD BugtrackerQCAD (main)Feature RequestLow Layer > Select Layer: add feedback ClosedCVH Task Description

Win 7
Q-CAD 3.19.2

R-Click in Layer list
With a selection, selecting by Layer adds the Items on that Layer to the selection.
With a selection, deselecting by Layer subtracts the Items on that Layer from the selection.
This is not a bug in casu because this can be the intention of the function. Adding or Subtracting.

Intuitively ‘selecting by Layer’ to retrict to that Layer solely has only the desired effect if no selection existed before.
Deselecting by Layer with no previous selection should mention there was none to start with.
Selecting by Layer from an empty Layer should mention that nothing is added.

Faults are prone to make.

Selecting a Layer uniquely would be an interesting additional feature.


1749QCAD BugtrackerQCAD (main)Feature RequestLowAdd support for non-uniform block scalingAssigned1CVH Task Description

Same txt as on the forum.
had a copy because i had to log in 3 times to remark my own post.

Blocks are no solution either.

see pdf
[attachment=0]Block test_1.pdf[/attachment]

Antartica is put in a block as segments.
Added a rounded corner as segments and as poly.
scaled X x0.5 Y x1 origin the center of the magenta circl.

The scaled version is all over the place.
Set them to color red, no use they stay black.

The reference of the block is 2000mm to the left because I tried it out far right of my design.
The cyan circle is about 400mm in diameter.

dxf part included
[attachment=1]Block test.dxf[/attachment]

Version: (3.20.1)
Build Date: Apr 13 2018
Revision: dd51609
Qt Version: 5.5.1
Architecture: i386
Compiler: MSVC++ 10.0 (2010)


 1752 QCAD BugtrackerQCAD (main)Bug ReportLow Not selecting text with sub/superscript ClosedCVH Task Description

Found a strange behaviour with formatted text.

File attached.
‘Draw’-selecting only the yellow text with a little space arround it
- L>R or R>L ⇒ Yellow text not selected.

‘Draw’-selecting only the yellow text with a little space from R>L but crossing the text half way
- Yellow text Selected ⇒ Expected behaviour.

‘Draw’-selecting just including the mentioned little circles.
- Orange L>R or R>L ⇒ Normal texts selected ⇒ Expected behaviour
- Green L>R Yellow not R>L Yellow selected ⇒ Expected behaviour
- Magenta L>R or R>L ⇒ Yellow text not selected ??
- Red L>R or R>L ⇒ Yellow text not selected ??

Version: (3.20.1)
Build Date: Apr 13 2018
Revision: dd51609
Qt Version: 5.5.1
Architecture: i386
Compiler: MSVC++ 10.0 (2010)
Windows 7 32-bit

Kind Regards

1755QCAD BugtrackerQCAD (main)Feature RequestLowSelecting standard rotation angles by mouse click for M...Assigned1CVH Task Description

This would be nice.
It will save a lot mouse - keypad changes for me.

 1756 QCAD BugtrackerQCAD (main)Bug ReportLow Polyline area wrong if polyline contains arc segments ClosedCVH Task Description

The area of polylines with arcs can be incorrect.
With only line segments it is correct as far as I can check.
See <Poly-line Area.dxf> ; <Poly-arc Area.dxf>

It does not depend on the quadrant their in nor with what point the start point is.
It is related with the oriëntation.
Flipping or mirroring horizontally induce the error.

Modifications like flip, move & copy may induce another error that locks the oriëntation.
It is noticed that the oriëntation property in the editor does not change anymore when reversing.
Although locked the value of the area property switches between good and wrong.

The master poly in question is a part of an arc and a part of an ellipse exploded 1024/full.
These where recombined to one poly with ‘Create from selection’ and are closed.
Closed as per the last vertex does not point to the start point, logically closed I presume.
The purpose is to sum the error surface for the skewing math.
For now I will use my common sence to distinguish what value is the correct one.
Reversing while found faulty is the solution.

Version: (3.20.1)
Build Date: Apr 13 2018
Revision: dd51609
Qt Version: 5.5.1
Architecture: i386
Compiler: MSVC++ 10.0 (2010)
Win7 32bit


 1757 QCAD BugtrackerQCAD (main)Bug ReportLow Modify > Auto Trim: on polyline, followed by undo yield ...ClosedCVH Task Description

Breaking up self-intersecting Polys at segments crossing
can’t be done for the second segment.

A new node is inserted and made start and end node.
For the second segment no division occurs or can be made.
Expected is that the segment the nearest to the selecting point is addressed.
Eg. the trim command.

Breakout gap:
- 1 Part fully trimmend of
- Can be undone

Auto trim:
(hint: do file-save first to revert)
- 1 Part fully trimmend of
- Undo will wipe the complete poly

In the file example 1.

- Divide
- Insert node on the second segment not at the crossing
- Divide at that node
- Move new nodes to crossing

QCAD 3.20.1 Win7 32bit
Kind Regards

 1761 QCAD BugtrackerQCAD (main)Bug ReportLow Info Polyline area does not find polylines (II) ClosedCVH Task Description

Selecting Info // Polyline area
And hovering over a drawing with all kinds of entities.
Does not find any polyline on the drawing hovering over them.
Nor clicking on them.

Not a locked layer issue.
All are visible.

 1763 QCAD BugtrackerQCAD (main)Feature RequestLow Simple Modify Move function ClosedCVH Task Description

Moving things require an extra click on ‘Delete original’ and a click on ‘OK’

A simple Modify Move functionality will reduce mouseclicks for moving by 2 for every move that is made.


 1768 QCAD BugtrackerQCAD (main)Bug ReportLow Draw > Polyline > Create From Segments: segments delete ...Closed1CVH Task Description

‘Create From Segments’ ‘OG’ includes and admits selection of segments on locked layers.

-When selecting a segment on a not locked layer it can include segments on locked layers that connect to the string. (Assumed wrong)
-A copy of the segments on the locked layer(s) are included in the polyline. (Assumed wrong)
These segments are not removed from the locked layer(s) because of their locked nature. (Intended behaviour)
eg. ‘OG’ & selecting the arc at point A in the example file. The arc is on a not locked layer.

-When selecting a segment on a locked layer it will fully remove segments that connect to the string on not locked layers. (Assumed very wrong)
-Connecting segments on the locked layer(s) will not be converted to a polyline because of their locked nature. (Intended behaviour)
eg. ‘OG’ & selecting the line at point B in the example file. The cyan lines are on a locked Layer.

Both A & B can be undone.

The example is a part of the ‘Skewing project’.


 1802 QCAD BugtrackerQCAD (main)Bug ReportLow Startpoint indication disapears for some entities while ...ClosedCVH Task Description

Having a multi selection and at least one ‘older’ arc the startpoint indication in red of some entities might disappear.

Entities that suffer from this are:
Other arcs

Only the ‘oldest’ arc in selection will have a startpoit indication.
Multi selection of ‘newer’ entities from the list above will not if an ‘older’ arc is part of the selection.
Deselecting de ‘older’ arcs will reveal the startpoints up to the ‘oldest’ arc.

In the file provided entities where drew in order from left to right.
Select all and start deseleting arcs from the left.

The behaviour is affected by changing the draw order property and a save/close/open.
In the second file the rightmost arc was set to draw order 7, the same as the 4th was.
After save/close/open it is renumbered to 8 and the behaviour is different as in the firts file.


 1906 QCAD BugtrackerQCAD (main)Bug ReportLow Draw > Polyline > Polyline from Segments: Converting fu ...ClosedCVH Task Description


Full 360 degrees Arcs don’t convert correct to polylines with the methods OG and OC.
Both methods create a zero-length open type Polyline and remove the full Arc.
OG creates a Poly with 2 vertexes at the startpoint (= endpoint) and OC one with 0 (zero!) vertexes.
The firts one is selectable, the second one only with ‘Select All’//TA because there are no references.

The OL method with the same start and endpoint doens’t affect the full arc.
Neither a poly is created nor an error is generated that the method failed.

Typical the bulge of the OG method is (-)16331239353195370, the OC method has no references.
The math to calculate the bulge should result in a division by zero or an illegal function as tan(π/2).
Therefore a polyline can’t contain a 360 degrees arc by standard means.

From the OC method is known that it simplify coradial arc strings to a single arc.
This should not result in 360 degrees arcs what would result in zero-length segments.
(With CAM fuzzy things may happen at such positions)

Simplifying coradial arcs strings that would create a 360 degrees arc should result in no less then two coradial Arcs.
The OG method will then creates a open Poly with 3 vertexes, OC a closed one with 2 vertexes.

Found while fiddling around with editing CXF fonts.
CXF uses full Arcs, two half arcs and even polylines with coradial segments that forms circles are supported,
the OC closed polyline with 2 vertexes is recoded as two 180 degree Arcs (90-270&270-90).


 1918 QCAD BugtrackerQCAD (main)Bug ReportLow Splines whit control points of order 1 and 4 not select ...ClosedCVH Task Description

Set up a spline with control points let’s say of the order 3.
Clone it 3 times with some offset in x&y.
Edit the degree property and set 1ste to 1, 2nd to 2, aso
Draw select partially from right to left.
Those of the order 1 and 4 aren’t selected.


 1924 QCAD BugtrackerQCAD (main)Bug ReportLow SweepAngle = 0 ClosedCVH Task Description

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.


 1925 QCAD BugtrackerQCAD (main)SuggestionLow Poly Ref Points manipulation that generates null-segmen ...ClosedCVH Task Description

Win7pro 32bit Wininstaller Qcadpro 3.23.0

With a polyline.

Select the poly.
Pick any reference point of a vertex.
Place it on any of its neighboring vertex reference points.

A null-segment is created.
The placement can not be undone by re-picking the reference point.
Can be Undone/Redone.
The action can result from editing the vertex coordinates.
When exploding null-entities are created.

This action should delete:
- if the target is next: the picked vertex. (incl. start or end-1)
- if the target is prior: the targetted vertex. (incl. start or end-1)
- if the target is and next and prior: both the prior and the picked vertex.

As the user intentionally places any vertex reference points on:
- any excluding its neighbors:
→ the intented nature is ‘Self-Touching’, ‘Self-Crossing’ or ‘Trace-Back’.
- any of its neighbors:
→ the intention is to delete the segment(s).


1928QCAD BugtrackerQCAD (main)Feature RequestLowOptionnally 'Auto clean up' after generation of NaN / N...Assigned1CVH Task Description

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.

If it can’t be undone by Undo/Redo it is a bug.

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

1976QCAD BugtrackerQCAD (main)Feature RequestLowEnvelope at offset to a poly toolAssignedCVH Task Description


1983QCAD BugtrackerQCAD (main)Feature RequestLowTrim All or Bulk Break outAssigned1CVH Task Description

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:

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.


 1985 QCAD BugtrackerQCAD (main)Bug ReportLow Hatch dots are rendered as lines with fixed lenght of 0 ...ClosedCVH Task Description

With some unit and scale combinations dots rather look like dashes.

2016QCAD BugtrackerQCAD (main)Bug ReportLowOffsetting multi selection of polylines halts prematureAssignedCVH Task Description


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.


 2059 QCAD BugtrackerQCAD (main)Bug ReportLow Modify > Explode: Error with hatch in block with positi ...ClosedCVH Task Description

See Forum Topic:

Isolated in Reply:

Sorry forgot to mention.
Reported by User 2CV375 qcad/cam version (3.24.2) on Windows 10.
Reproduced in Qcad pro 3.24.2 on Windows 7/32.

 2078 QCAD BugtrackerQCAD (main)Bug ReportLow Draw > Hatch: Small gap tolerated by QCAD, not by DXF/D ...ClosedCVH Task Description

It seems to be an accuracy problem.
The original hatch boundaries are defined from 732 single entities.
These interconnect with an accuracy better then 1e-10 except for a gap of 0.000814 in two places.

Creating a Hatch of these entities with TA-HA is rather slow but succesfull.
After Save-Close-Open the Hatch may look different or may even be missing (=Null).

Suspected is that:
The recreation off the Hatch on load uses some other accuracy setting.
The outer boundary is not found and only some inner ones are considered as outer.

But that explains not why it looks fine after initial creation.
Nor that the outcome of a retry may vary.


 1607 QCAD BugtrackerQCAD (main)SuggestionVery Low Indent 'Spline Segments:' in explode preferences Closed1CVH Task Description

 FS#1604  was issued because of non-intuitive hierarchy of the preferences for the Explode function.
The task comment recieved explains the funcionallity in details not found elsewhere.

Indentation of the phrase ‘Spline Segments:’ suggest hierarchy.
Graying out the drop down box for the number of spline segments establish hierarchy.

 1759 QCAD BugtrackerQCAD (main)SuggestionVery Low Modify // .... selection of entities on locked layer al ...ClosedCVH Task Description

Without any selection.
Entities on a locked layer can be selected after choosing:

Asumed wrong
- Modify DI
- Modify
- Modify D3
- Modify

- Modify RM
- Modify
- Modify RN Less severe
- Modify
- Modify OH
- Modify


1760QCAD BugtrackerQCAD (main)Bug ReportVery LowSelf-crossing polylines can't be cut twice at segment c...AssignedCVH Task Description

Re-entering dividing problem from  FS#1757 

Divide the poly selecting near segment 1 at the segment crossing.
> A new node is inserted on the crossing and made start and end node.
Divide the poly again selecting near segment 2 at the segment crossing.
> no division appears to be done.

One can’t divide the second segment at the crossing

Presumed intended behaviour like  FS#1750 


 1762 QCAD BugtrackerQCAD (main)Bug ReportVery Low Modify // .... selection of entities on locked layer al ...ClosedCVH Task Description

Not served with the degration to ‘Suggestion’  FS#1759 .
Demanded closing  FS#1759  & re-entered

Locking entities (by layer) to avoid selection,eg. nearby,very close by or on the same spot, does not have the intended influence.

Asumed wrong:
- Modify DI
- Modify B2
- Modify D3
- Modify MT
These 4 need a single entity to be selected and selection of a locked entity is allowed.(=questionable)
The action will allways leed to ‘not allowed’.(=correct)

- Modify RM
- Modify CH
- Modify RN
These 3 need a pair of entities.
RM: Selection of a locked limiting entity is allowed (=questionable), enity to trim not.(=correct)
The action will trim unlocked entities to the locked limiter.(=questionable)
CH & RN: Selection of a pair of entities is allowed.(=questionable)
Trimming if ‘trim’ is on will not occur because locked and leeds to ‘not allowed’.(=correct)
The creation of the bevel or rounding on an active locked layer will not occur because locked and leeds to ‘not allowed’.(=correct)
The creation, except for polyline segments (because locked themself), on an active unlocked layer will be done.(=correct)

Less severe but still questionable: (because these don’t necerally act on the locked entities themselves)
- Modify OF
- Modify OH
- Modify SS
OF: Selection of a locked base entity is allowed.(=questionable)
The preview is casted only if the active layer is unlocked.(=correct)
The creation is only done on an active unlocked layer.(=correct)
OH: Selection of a locked base entity is allowed.(=questionable)
Selection of point references from entities on locked layers is allowed.(=questionable)
The preview is casted only if the active layer is unlocked.(=correct)
The creation is only done on an active unlocked layer.(=correct)
SS: Selection of point references from entities on locked layers is allowed.(=questionable)
Strechting is only done for unlocked entities. (=correct)

1765QCAD BugtrackerQCAD (main)Bug ReportVery LowErrors with polyline offsetAssigned1CVH Task Description

Win 7 32 bit QCAD 3.20.1

Ofsset of a base-line with arcs results in massive ammount of errors.
Most of them occur as a cluster of very tiny segments and are part of the offset. (zoom far in at the red circles)
Mostly they occur where the offsetted arcs should merely be trimmend pairwise.
Some occur as detached entities or as detached strings of entities very near the offset (strings not documented).
Spooks occur at opposite site when base-line is not closed.
360° curls can occur with R = Offset.
Null-entities may occur (not documented, hard to find and not able to copy).

The base-line is checked and sound and has mixed tangentially or not tangentially connected arcs.
Offsetting the mother base-line of the base in the file has similar effect but not all and/or different ones.
Also encountered with offseting polys from fonts.
Used to define pocket paths for CNC.
Detected because the CNC driver will not accept Self-crossers, Null-entities or open ends depending on the settings.

Work arround is to explode and select small entities but this does not solves the issues.
1) Choosing the tolerance large enough will detect small segments that should stay.
2) Recombining will generate new ones at the place where the main segments remain crossed.
Cleaning up the paths is a daunting process with some thousand segments for several offsets.

I assume this has an infuence on the CAM part of QCAD too unless the offset method is different.

1919QCAD BugtrackerQCAD (main)Bug ReportVery LowWrong order XY(Z) for Ordinate Dimension in property ed...AssignedCVH Task Description

Win7pro Qcad Pro

In property editor
properties of an Ordinate Dimension

Without Show Z
DefPoint is displayed in order YX?

With Show Z
Origin is displayed in order XZY?
DefPoint is displayed in order YZX?
LeaderEndPoint is displayed in order ZXY?


1923QCAD BugtrackerQCAD (main)Bug ReportVery LowFaulty rendering Polylines with Global/Local Widths and...AssignedCVH Task Description

Win7pro 32bit Qcad 3.23.0

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.


Showing tasks 1 - 37 of 37 Page 1 of 1

Available keyboard shortcuts


Task Details

Task Editing