All Projects

Andrew,

Please refer to related forum topic:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10724#p44206

An eighth circle with radius 8 Lead In/Out relates to nothing in the actual exported cutter trajectory.
Nor does it with the edge being cut.

Proper examples and a comparison with ‘Extension’ type Lead In/Out included.
Conclusion: IMHO connecting the cutter trajectory and edge being cut is wrong.

It looks a lot like turning on Cutter Compensation (G41/42) while the motion is circular.
But that is uncommon because most controllers can not cope with this motion.
One can increase the offset gradually along a straight pre-entry segment for turning on G41/42 but not along a circular path.
Also see snippet:
- Pre-entry C→B turning on G41
- Circular Lead In B→A

Regards,
CVH

Andrew,

Related topic: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10649

Already two different users report that Landscape is printed cropped in portrait format, both Win11. The behavior change occurred recently.
Although the second user (rdtsc) reports the same behavior for latest Mabox Linux (Manjaro, Arch.)

Can not replicate that on Win7 32 bit nor on Win10 64 bit, both are no longer or not updated OS. For one, I have no orientation setting displayed in my printer dialog.

It seems not to be related to the QCAD version:
Reported for:
- Win11 QCAD Pro 3.29
- Win11 QCAD-CAM 3.27.8.0

Regards,
CVH

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,

When we alter about any property of a Hatch entity it seems to be recreated with a newer/higher handle.
This doesn’t influence the drawing order in direct.
But already changing the drawing order of a Hatch it is recreated as a new entity.

It starts to matters in drawing order when there are multiple entities with the same drawing order and that after save/reload. Entities with the same drawing order then receive a new drawing order based on the original but sequentially increasing based on handle.

Because a Hatch is recreated with a newer/higher handle each time a property changes it will thus always end up above the others with the same order even when the original was created earlier.

This is more pronounced when copying/pasting entities from a source to a target drawing.
The original Hatch drawing order is retained but it will always be above existent entities with the same drawing order in the target drawing after save/reload.

Most other entities are probably just updated in situ.
It is unsure to me at this point if merely updating a Hatch is even possible.
And perhaps this is related to the addObject ForceNew flag what is false by default.

Regards,
CVH

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

For ‘milling’ on path it doesn’t consider

this.arcInterpolation = true

in the custom postprocessor nor the checked option in the CAM Configuration Dialog.

As far as detected the CamArcInterpolation checkbox of the CAM Configuration Dialog is unrelated to the this.arcInterpolation in the postprocessor.

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,

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

When entering 1’ 1’‘ in an input field.
- As the size of the rectangle in the topic
- As the length property of a line selected in the drawing
- ....

Returns 13 in a drawing in mm.
And also in a drawing in inch what turns out to be correct.
But also in a drawing in foot.

Similar, entering 1’ with a drawing in kilometers it returns 12 units = 12 kilometers.

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,

Usually I point to something to start with.
Sometimes I want to point away from here but then the arrow is where I just clicked.

An option on creation would be nice.
The capability to reverse the Leader orientation afterwards is another method to get it pointing the intended way.

A Leader entity is stored similar as a polyline.
I think it would not be difficult to reverse the basic polyline and update the dimension shape accordingly.

Regards,
CVH

Andrew,

When we use Lengthen/Shorten (LE) with a positive amount the result is clearly visible when indicating a side of an entity.
With a negative amount there is seemingly no preview.
It is generated and shown but one can not distinguish it especially with solid lines.

Adding an orthogonal auxiliary preview shape some N pixels long would do the trick.

Regards,
CVH

Andrew,

Unrelated to OS or QCAD version.

In the postprocessor configuration dialog there is a group box called ‘GroupCustom’.
One can add custom widgets to that, rename it and so on.

Such is not provided in CamProfileToolpathDialog.ui or CamDrillToolpathDialog.ui

It should be possible but we aren’t really able to mix up things with the ‘Message’ QLabel ...
A reserved QGroupBox would do the trick.

Related topic:
https://www.qcad.org/rsforum/viewtopic.php?f=74&t=9647

Regards,
CVH

Andrew,

When switching from Default to Dark mode the text on alternating rows is hardly visible.
We can customize this color.

It would be easier if a proper default color is set on switching to and back.

Perhaps the user preferences can be remembered.
Perhaps only when the contrast would be affected.

Regards,
CVH

Andrew,

Not OS or Version depending.

We can’t filter on some specific properties of polylines.

Handy would be:
- Global Width
- Orientation

Specific:
- Polyline Pattern
But I don’t really search for them ... For some post-op I just need them all to be set to ‘No’.
- # of vertices
Filtering the complex from the more simple ones.
- Including Bulges or not
To seperate polylines with arc segments form others.
There some operations that don’t really work with bulging.
- Z values and/or global Z
This would make sense for some but filtering on Z is not common under QCAD as it is 2D.

Regards,
CVH

Andrew,

Changing orientation of a polyline with RV or by changing it in the Property Editor clears the global width value.

Single line pieces as polyline default to CCW.
Still the global width is cleared when trying to set them CW.

I didn’t update since 3.27.0 but reading this topic I suppose it still is valid.
Related: https://www.qcad.org/rsforum/viewtopic.php?f=89&t=9362

Regards,
CVH

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

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

Include RPolyline.getLeftRightOutline() method in class_r_polyline.html

In use since 11 Sept 2020

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

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

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

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

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

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

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

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

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

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.

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

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

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

Andrew,

One Microinch is equivalent to 25.4 nanometers and I don’t consider that to be metric.

RUnit.isMetric(this.getDocument().getUnit()) returns true for RS.Microinch or value 8.

https://github.com/qcad/qcad/blob/master/src/core/RUnit.cpp#L145-L155
Returns false for: RS::Inch ; RS::Foot ; RS::Mile ; RS::Mil ; RS::Yard
... and true for all the rest.

Also see last note in: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=9506&p=38295

Not to be confused with RDocument::isMetric() because that returns the measurement system unless that is RS::UnknownMeasurement what is rather impossible with drawings created by QCAD.

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

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,
On behalf of user Kmeelo

Polygonal Area adds measurements text with 12 decimal digits and then as short as possible.

Current formatting path see: https://www.qcad.org/rsforum/viewtopic.php?f=32&t=10450&p=42833#p42805

Related forum feature request: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10458

I also see a misconception of the term ‘precision’.
Numbers precision is the amount of significant digits disregarding the position of the decimal point.
12 decimal digits is about the largest precision for numbers with 5 integer digits.

Regards,
CVH

Andrew,

See attachment with example:

Solution included on layer ‘Solution’.

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,

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,

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

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

QCAD Professional
Win7 WinInstaller 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

Related forum Topic:
https://qcad.org/rsforum/viewtopic.php?t=8015

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 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.4 (3.25.2.4)
Internet: QCAD.org
Build Date: Nov 18 2020
Revision: 40f4475
Qt Version:5.13.2
Architecture: i386
Compiler: Unknown

Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757
Splitting the old report up ...
Same file.
In the left example one can auto trim (AX):
- The lower loop.
- The top loop.
Bug?
The action on the top loop can’t be undone.

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

Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757
Splitting the old report up ...
Same file.
In the left example one can break out segment (D2):
- removing one of the loops with the ‘remove’ option.
- leaving both without the ‘remove’ option.
Bug?
Without the ‘remove’ option it can’t be undone.

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

Continued from https://qcad.org/bugtracker/index.php?do=details&task_id=1757
Splitting the old report up ...
Same file.
In the left example one can cut (DI) once.
Cutting the second segment results in NO cut.

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

Related topic: https://qcad.org/rsforum/viewtopic.php?f=33&t=7882
Explanation found in REntity.cpp
Listed as a Public Member Functions inherited from RObject

Regards,
CVH

Summary: Block zoomstate supersedes Model_Space after Undo of BC

QCAD Professional
Version: 3.25.2.1 (3.25.2.1)
Internet: QCAD.org
Build Date: Oct 15 2020
Revision: 2895712
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown «< (Win installer 32 bit)

With the file provided:
ZW to see the top green ‘revision cloud’ up close
QQ
Box select around the cloud
»> 2 entities in selection
BC, select origin somewhere inside the selection, accept proposed naming
»> ‘Block 1’ is created from the selection
TN
BD, select the newly created Block Reference
»> Auto zoom of ‘Block 1’ (Intended behavior)
OO
»> Returns to Model_Space with the zoomstate of the removed Block
»> Halfway down the drawing
»> The former zoomstate of the Model_Space is lost

Intended behavior is that the zoomstate of Model_Space and Blocks don’t mix
See: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=7797&p=30371#p30378

This proves they do, even if the block doesn’t exists anymore.

Regards,
CVH

PS: 3th trial to enter a suggestion ...

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