QCAD Bugtracker

Please refer to: https://www.qcad.org/rsforum/viewtopic.php?f=74&t=9033

Regarding to forum post:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8982&p=35836#p35836

dwg loaded in 3.27.1 frees QCAD (no response) and a Win10 PC. Same drawing loaded in 3.26.0 causes no problems. It looks to me that two hatches (handle 198b6, 198ba) are the culprits.
Drawing saved without those hatches opens without any problem in 3.27.1.

TECNOFLEX symbol library.dwg = original file from forum post
TECNOFLEX symbol library_mod.dwg = my modification

Headline should already explain the issue ...

1. Create spline
2. Move spline nodes. After ~10 times move qcad is crashed with backtrace:
Thread 9 “Thread (pooled)” received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff56dc9640 (LWP 8224)]
0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848) at /usr/include/qt5/QtCore/qlist.h:492
492 current→v = new T(*reinterpret_cast<T*>(src→v));
(gdb) bt
#0 0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848)

  at /usr/include/qt5/QtCore/qlist.h:492

#1 QList<QSharedPointer<RShape> >::detach_helper (alloc=<optimized out>, this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:835
#2 QList<QSharedPointer<RShape> >::detach_helper (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:849
#3 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178
#4 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178
#5 0x00007ffff686182a in QList<QSharedPointer<RShape> >::end (this=<optimized out>, this=<optimized out>) at /usr/include/qt5/QtCore/qlist.h:342
#6 QList<QSharedPointer<RShape> >::last (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:364
#7 RSpline::appendToExploded (this=0×555557311510, line=...) at math/RSpline.cpp:964
#8 0x00007ffff6867059 in RSpline::getExploded (this=0×555557311510, segments=1457293328) at math/RSpline.cpp:919
#9 0x00007ffff686682a in RSpline::getLength (this=this@entry=0×555557311510) at math/RSpline.cpp:1026
#10 0x00007ffff6c11490 in RSplineData::getLength (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineData.h:178
#11 RSplineEntity::getProperty (this=0x5555573114a0, propertyTypeId=..., humanReadable=<optimized out>, noAttributes=<optimized out>,

  showOnRequest=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineEntity.cpp:253

#12 0x00007ffff67cc214 in RPropertyEditor::computePropertyValue (ccProp=...) at /usr/src/debug/qcad-3.27.0.0/src/core/RPropertyEditor.cpp:574
#13 0x00007ffff67d298f in QtConcurrent::FunctionWrapper1<void, RProperty&>::operator() (u=..., this=0x555557757f18)

  at /usr/include/qt5/QtConcurrent/qtconcurrentfunctionwrappers.h:80

#14 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIteration (it=..., this=0x555557757ee0)

  at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:68

#15 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIterations (this=0x555557757ee0,

  sequenceBeginIterator=..., beginIndex=<optimized out>, endIndex=15) at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:77

#16 0x00007ffff67d2c9d in QtConcurrent::IterateKernel<QList<RProperty>::iterator, void>::forThreadFunction (this=0x555557757ee0)

  at /usr/include/qt5/QtConcurrent/qtconcurrentiteratekernel.h:255

#17 0x00007ffff44b5b2d in QtConcurrent::ThreadEngineBase::run (this=0x555557757f20) at qtconcurrentthreadengine.cpp:302
#18 0x00007ffff59c8d52 in QThreadPoolThread::run (this=0x555556198b10) at thread/qthreadpool.cpp:100
#19 0x00007ffff59c5a61 in QThreadPrivate::start (arg=0x555556198b10) at thread/qthread_unix.cpp:329
#20 0x00007ffff546c717 in start_thread (arg=<optimized out>) at pthread_create.c:435
#21 0x00007ffff54f018c in clone3 () from /lib64/libc.so.6
(

It would be helpful if the scale field that appears while placing a viewport would also re-appear when the viewport is selected after it’s already been placed in the layout. It would also be helpful if the pre-populated values in the dropdown matched those in the global layout scale field.

The inside corners of profile tool paths have rounded inside corners. This occurs because the rounded outside the bit cannot make it all the way into the corner of the feature. Think of tracing the inside wall of a cardboard box with a can of soup. The can makes direct contact with the box walls, but its
round shape is unable to completely fit into the tight corners— there’s always a gap.

In a dog-bone overcut (see the figure in attachment), the inside profile corner is enlarged into a semicircle, allowing the sharp edges of the mating piece to slide through without interference.

When a dog bone is applied to the inside corners, as shown in the second figure in the attachment, the joints fit together nicely!

The following website explains what should be implemented More elegant CNC dogbones

There are two ways to implement this tool. Either you modify the original design (as implemented in Fusion 360) or you can do it at the moment you define the tool path (Estlcam allows you to do this for example). See the feature Corner overcut, on Estlcam website

Hi,

I believe prior QCAD version 3.22.0.0 there was no rotating preview. The rotating preview shows the outcome regarding to the chosen center point. I know that it is also common for move/copy. However, for me it is very confusing and difficult to chose the correct center point for a rotation if I’m constantly been distracted by the most of the time overlapping preview of my selection. This said if the drawing is very detailed I have to zoom in extremely to be able to snap to the right entity. That wouldn’t be necessary without the preview. Additional rotate a large drawing selections will compromise the performance - CPU is going like crazy.

It would be nice to have an option to turn this preview on/off.

Add a tool to duplicate a layout block with contents.

Multiline attributes can contain linefeeds and formatting like MTEXT.

Would be nice to change default font type and size for command line widget.

I’m used to have persistant selection while drawing (Application Preferences > Graphics View:Appearance > Selection), but I’m missing deselection of all objects with ESC key. I have seen the option to deselect with right key, but it’s nice to have right key for context menu.

Currently ESC key cancels current active command, but would be nice if there is no command active to also deselect all features by default.

I tried to assign double click on middle-mouse button to zoomauto command, but it seems it’s not possible currently.

Would love to see this feature.

Would it be possible to extend the tool for importing points with a label so that when importing points into the drawing (as it is now), the attributes of the point are taken from the csv file and written to the point’s own properties? See attachment. This would extend the functionality of the tool and I assume that it would also lay the foundation for the possible re-export of such points from the drawing to a csv file, including all the details.

When using the vertical line tool, you can enter a length value in the options toolbar, then place the line. If you want to change the length, you just need to enter a new value and the length field will update. However, there seem to be cases where after 10-20 entries, the focus goes off the length field in the options toolbar, requiring the user to bring focus back to continue. I could not seem to duplicate this behavior with the horizontal line tool.

The option of a layer state widget would be a nice way to see and select between different layer states.

I have set the grid/snap value to X=.0625 Y=.0625 on all 4 viewports.
When zooming in and out the grid/snap scale changes from .0625 to 3.90625. at this point the grid/snap points differ,
This causes a variation in the grid/snap reference points lending to drawing errors.

example
When I use the grid settings defaults .01, when zooming in and out, the grid/snap scaling doesn’t seem to have this issue.
Other values do, See below.

set value first zoom second zoom next zoom

	point		point		point ...	

0.01 0.1 1.0 10.0 ...
0.02 0.04 0.4 4.0 ...
0.04 0.16 1.6 16.0 ...
0.05 0.25 2.5 25.0 ...
0.0625 0.390625 3.90625 39.0625 ...
0.0254 0.64516 6.4516 64.516 ...

Why is there a squaring of the original set value? Which then becomes a new zoomed grid/snap value?

QCAD Professional
Version: 3.26.4.0 (3.26.4)
Internet: QCAD.org
Build Date: Jun 3 2021
Revision: 0bb4334
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

As a heavy mechanical drawings user, it would help a lot to have an option to exit a block saving as a new name and making it a new entity from that time ahead.

Example: if a have a lot of screws, one of then is behind another peace and need the to have some lines changed to hidden style lines, in the flow of the work is great if I edit that screw in place and when exiting have the option to save as a new block, to don’t mess with other entities of the same block that I don’t want to change. Yes, there is a workaround that is duplicate and rename the block prior to the editing, but a save as seems to work easier.

Thanks Andrew and team!

In the US, it is (unfortunately) still common to use US survey foot. It seems at least some DXF applications/libraries support this unit as a $INSUNITS value, some references:

• https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2020/ENU/AutoCAD-Core/files/GUID-A58A87BB-482B-4042-A00A-EEF55A2B4FD8-htm.html
• https://ezdxf.readthedocs.io/en/stable/concepts/units.html#insunits

There are two issues regarding this with QCAD:

1. If you open a document with $INSUNITS being 21, it’s reset to 0 (unitless/unspecified) when saved again, even when not changing anything.
2. It is not possible to select these units in the GUI.

I don’t know about standardization of these values, but my hope is that it’s at least possible to preserve the unit in an existing drawing. Given that this unit is supposed to be obsolete in some years, it might seem less important, but due to this transition, it might get even more important to be able to distinguish between units. Thanks!

no task description

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

See also:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8531

It would be a very interesting feature to add to future versions.

I also use AutoCAD Mechanical 2012 and the BOM is synced with every balloon on the drawing. Making it easy to edit.

The core BOM accepts formula fields and we can easily calculate the mass of a part, with some Ifs and math.

The BOM that is shown in the actual drawing is more simplistic, and has just Part number, Quantity, Mass and the Description. But it’s related to the “core BOM”.

It’s a very interesting thing! It would be great on QCad.

I’m often in the situation that I have to select for nesting 50+ sheets. Currently is only a Shift + left mouse click selection possible. It would be nice if QCAD/CAM could get for the nesting / sheet selection additional a mouse rectangle area selection.

Angle Display is decimal although the decimal display is disabled in Application Preferences.

Format should be 17° 31’ 52” instead of 17.531111.

See also:
https://www.qcad.org/rsforum/viewtopic.php?f=2&t=8342

When I modify partly a DIM with “Stretch” or changing one Extension line position with drag and drop the Value text is updated which is nice working. Unfortunately the previous value stays in place and is overwritten by the actual value. I think for a good readability the previous value should disappear in the moment when the new value is presented.

Hello dear CAM developers!

I need to use the same tool at different spindle speed in a single machining file.
I would deeply appreciate if you could add a Spindle Speed edit field in the CAM Profile Toolpath edit window in order that each Toolpath can have its own Spindle Speed value (same as you did for Feed Rate and Plunge Rate)

FYI, the tool on my concern is a laser who’s power is driven by the Spindle Speed PWM signal.
I need to be able to do both engraving and cutting in a single file.
Alas! this laser tool is defined with a fix and unique number (99).
Therefore I cannot define different laser tools with different speeds.

Many thanks
Best regards.

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.

When saving a view, it would be great if the view also saved which block (model space, layout block, or any other block) that was active at the time the view was saved and when the view is later re-activated, the corresponding block would re-activate.

The “Define annge using mouse cursor” of the Rotate tool would be useful in the Move and Rotate Tool

Add functions to the Reorder tool, similar to the functions of the counter tool, undo last step and start at any number, allowing corrections and restarting the tool part way through.

See the discussions at https://qcad.org/rsforum/viewtopic.php?f=32&t=8170

The option for vertically and diagonally stacked fractions would be helpful for both the text creation tool and as the output of dimensions.

Select the previously selected entities.

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

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!

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

With a Mac (and no external mouse) there’s no middle button so it’s not possible to pan the 3D view (that’s what they tell me in the forum). It would be useful if one could use command-drag or control-drag to pan around the 3D view.

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

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.

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

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.

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

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