QCAD Bugtracker

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

When I zoom, the text disappears in certain zoom levels after updating to the latest version.

I would like to request a new kind of snap: a “Restricted Intersection” snap that appears at the point where an entity would intersect with a line drawn from Relative Zero that fulfills the current EL criteria. “Restricted Intersection” snaps would be similar to other Relative Zero-based snaps (like “Perpendicular” and “Tangential”), but would predict the point of the snap from the EL constraints instead of the characteristics of the entity being snapped to. Naturally a value of 0 for angle or length would result in that constraint being ignored.

Additional operational flexibility could be achieved by allowing the snap to exist regardless of whether EL is actually in use. To be useful this would probably require determining snap locations based on angle OR length as opposed to angle AND length.

Implementing this new snap would allow, for example, for easily drawing a line of unknown (but determinable) length at a specified angle between a given point and a given entity (see discussion here), with the “Restricted Intersection” snap ensuring that the endpoint of the new line forms an intersection with the entity in question. Currently the same goal can be achieved a couple of different ways, but they all involve at least two separate steps.

This is either a bug or a feature request, depending on perspective; my apologies if I’ve picked the wrong one. Additional discussion can be found here.

Steps to reproduce:
1. Create an entity
2. Run “Create Library Item” [BT]
3. Select Reference Point

Expected outcome:
“Save As” dialogue opens in the directory that the previous library item was saved in

Actual outcome:
“Save As” dialogue opens in ( RSettings.getLaunchPath() + “/libraries” )

Additional Context:
The reason I’ve categorized this as a bug is because, relative to the behaviour of the main “Save As” dialogue (which does remember the last directory used) the behaviour of the “Create Library Item” “Save As” dialogue is unexpected.

Software versions:
QCAD 3.25.2 Pro
Windows 10 Pro

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

Looks like error, but may be that’s feature request.

CAD software uses typical navigation behavior as:
Wheel = Zoom; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right.

Any other software like browsers, office software (openoffice writer, ms excel and so on), 2d paint software like GIMP (Photoshop and so on) uses other behavior:
Wheel = Scroll up/down; Ctrl+Wheel = Zoom; Shift+Wheel = Scroll left/right.

Users, that intensively use CAD and other software simultaneously prefer to make same behavior in their applications switching CAD scroll to plain mouse wheel.

QCAD’s “Application Preferences”: “Graphics View: Navigation”: “Mouse wheel/ two finger swipe”: “Scroll” allow user to assign scroll up/down to wheel mouse instead of Zoom. But there is mistake Ctrl+Wheel didn’t change to Zoom. Ctrl+Wheel continues to scroll up/down, as the wheel.
Wheel = Scroll up/down; Ctrl+Wheel = Scroll up/down; Shift+Wheel = Scroll left/right. No zoom!

Draw manipulation at this mode like a hell: you need to use wheel in conjunction with Ctrl/Shift to point draw in desired position, than move your hand to +(-) for make desired zoom.

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

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

When placing a hole at x0 y0 there is no G00 x0 y0 in the exported G-Code.
So the first cut was made at the current position of the tool, not at x0 y0!

Add alpha property to filter for hatches.

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