QCAD.org Forum

Only for those who aren't offended by constructive contributions,
documented numerous shortcomings. And solved all of them, and many more in the process.

A) End 2019 I had an issue with an explosion of a bulging Polyline with local Widths:
viewtopic.php?t=6853
https://www.ribbonsoft.com/bugtracker/i ... sk_id=2023
What is fixed in later releases.

B) Also resulting from this and since 11 Sept 2020 the outlines are in general no longer closed Polylines

C) The explosion of such have many flaws although the newer RPolyline.getLeftRightOutline() method
is a far better representation for bulging Polylines with changing Widths.
In 3.24 the method was: RPolyline.getOutline()
Exploded these are most correct at present day ... less than 0.01%R off.
Status 12/01/2020: The method is NOT yet documented >>
https://www.qcad.org/doc/qcad/latest/de ... yline.html

D) Minute length with A) or almost Null-length entities at zero Width.
(1/1/21) https://www.ribbonsoft.com/bugtracker/i ... sk_id=2168

E) Specific 2R render wrong and explode to nothing.
(13/12/20) https://qcad.org/rsforum/viewtopic.php? ... 889#p30803
(20/12/20) https://www.ribbonsoft.com/bugtracker/i ... sk_id=2155
Prior to Sept 2020 these exploded 'as is' rendered.

Solved all that, the GUI explode method at least, see file: Bug report with solution(s) included:
https://www.ribbonsoft.com/bugtracker/i ... sk_id=2174

Meanwhile, solved all splines from text:
- https://qcad.org/rsforum/viewtopic.php?t=6458

Adapted to Andrew's latest and more persistent circle explosion preference fix:
- https://qcad.org/rsforum/viewtopic.php?t=7914
- https://qcad.org/bugtracker/index.php?d ... sk_id=2156

Final implementation is only at Andrew's discretion ...
One could vote for it at QCAD Bugtracker.
Requested closure of all related Bugs/Features/Suggestions


Don't reply (argue) on this post because I will not be notified - might not read it.
On Andrew's proposition/request I opted out.
A PM might still reach me.

CVH