|
2495 | ECMAScript | Bug Report | Very Low | RLine.isParallel(RLine) may return true for certain non... | Assigned | |
1 |
Task Description
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
|
|
2497 | QCAD (main) | Bug Report | Very Low | Draw > Circle > 3 Tangents (CT3) fails in some cases wi... | Assigned | |
1 |
Task Description
Andrew,
See attachment with example:
Solution included on layer ‘Solution’.
Regards, CVH
|
|
2501 | QCAD (main) | Feature Request | Very Low | Add spelling checker / spell checker for all text boxes | Assigned | |
1 |
Task Description
Suggestion to add spelling checker / spell checker for all text boxes
|
|
2505 | QCAD (main) | Feature Request | Very Low | Info > Polygonal Area > Use dimension decimal format fo... | Assigned | |
1 |
Task Description
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
|
|
2538 | QCAD (main) | Bug Report | Very Low | Weight 2.11 French translation typo | Assigned | |
1 |
Task Description
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
|
|
2539 | QCAD (main) | Bug Report | Very Low | (Relative) Polar feet + surveyor notation fails. | Assigned | |
1 |
Task Description
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
|
|
2541 | QCAD (main) | Suggestion | Very Low | Consider the unit "Microinch" to be non-metric | Assigned | |
1 |
Task Description
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
|
|
2544 | QCAD (main) | Feature Request | Very Low | Request to add "plain text" paste, traditionally CTRL-S... | Assigned | |
2 |
Task Description
See: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10379
Could you add “plain text paste” as ctrl-shift-V Why? Because sometimes the clipboard comes in with rich text formatting that’s anti-helpful. The workaround is to paste into a plain text editor, or the console, then recopy and repaste into qCad.
Either way the ctrl-shift-V shortcut is useful for those trained on other software but: one could also argue that qCad should NEVER take rich text, and rather only accept the plain text with both CTRL-V and CTRL-SHIFT-V.
— CHV says
Agreed, having encountered it numerous times while documenting with text snippets from elsewhere. :roll: Even copying Info measurements from the Command Line are Rich Text.
The best place to file a feature request is QCAD Bugtracker: https://www.ribbonsoft.com/bugtracker/ You may need a different account there or make a new one.
May I remark that Ctrl-Shift-V is already in use for Paste along Entity (PE) But not when the Text Editor Widget has the focus and dialog Widgets are always modal on a Win OS system. :wink: Still, I’ll vote for it in any way.:P
Regards, CVH
|
|
2547 | QCAD (main) | Bug Report | Very Low | Block > Purge Unused Blocks > Removes _DatumFilled bloc... | Assigned | |
1 |
Task Description
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
|
|
2557 | QCAD/CAM | Suggestion | Very Low | G20/21 not occuring in generic postprocessors | Assigned | |
|
Task Description
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
|
|
1285 | QCAD (main) | Feature Request | Low | Property Painter | Researching | |
2 |
Task Description
Easy transfer of properties from one entity to others
|
|
2125 | QCAD (main) | Bug Report | Low | Text disappears when you zoom | Waiting on User | |
|
Task Description
When I zoom, the text disappears in certain zoom levels after updating to the latest version.
|
|
2558 | QCAD/CAM | Bug Report | Low | Offset trajectory path issue with circular Lead In/Out | Waiting on User | |
|
Task Description
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
|
|
2494 | QCAD (main) | Bug Report | Very Low | Information scrip on drawing screen unaligned. | Waiting on User | |
|
Task Description
Please view the attachment.
Regards
Graeme
|
|
693 | QCAD (main) | Feature Request | Medium | Support for external references (XREF) | Likely to be implemented | |
28 |
Task Description
Support for external references (XREF)
|
|
1127 | QCAD (main) | Feature Request | Low | Leaders: spline shaped | Likely to be implemented | |
2 |
Task Description
Add support for spline shaped leaders
|
|
1224 | QCAD (main) | Feature Request | Low | Revision clouds | Likely to be implemented | |
9 |
Task Description
Add support to draw revision clouds or convert polylines, ellipses, circles to revision clouds.
|
|
2205 | QCAD (main) | Bug Report | Low | Text rendering fails in certain zoom level | Waiting on fix in 3rd party library | |
1 |
Task Description
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.
|