QCAD Bugtracker

Andrew,

simple_modify.js
function paste()
10 * \param docDestination RDocument to paste into (or undefined for current document)

A) This should be a document interface of the type RDocumentInterface.
B) The function uses the parameter diDestination and not docDestination

https://www.qcad.org/rsforum/viewtopic.php?f=30&t=9742

Regards,
CVH

Case: Launch Print preview (first time), confirm dialog “Auto fit drawing to paper?” with yes, change after that the scale, close Print Preview, launch Print Preview - the last chosen scale what should be remembered is overwritten by the Auto fit scale.

Note:
The Auto fit scale stays persistent - even after reloading the drawing!

The option “Auto fit drawing to paper?” as a dialog occurs only the first time you use Print Preview - there is no way to change the chosen option later in a session or after reloading the drawing ...

Andrew,

Seems to be a copy/paste but never re-edited kind of mistake.

Quick fix:
https://github.com/qcad/qcad/blob/master/scripts/Misc/MiscInformation/InfoCentroids/InfoAreaCentroid/InfoAreaCentroid.js#L1320 line 1320 should read:
return [centerPoint.x, centerPoint.y, centerPoint, radius*radius * Math.PI];

line 1318 was intended to replace the ‘area’ portion of line 1320 literally.
As is, the code in this line makes no sense and line 1318 should be removed.

Still have to investigate if the area of a full 360° arc sector/segment should be signed ...
... and if RS.AngleTolerance is required when comparing.

Regards,
CVH

Andrew,

Hatches in uniform scaled blocks explode perfect among other entities, even a hatch pattern is scaled.
Hatches in non-uniform scaled blocks are exploded as not scaled.

One could scale the hatch boundaries non-uniform.
For solid hatches the pattern scale doesn’t matter.
For patterned hatches the pattern scale and angle is more problematic.
But why not explode it as is, the pattern is transformed as expected for the non-uniform scaled block reference.

Or one doesn’t transform the pattern at all but then the the non-uniform scaled block reference isn’t displayed correctly.

Regards,
CVH

Version: qcad-3.27.9.3-alt1
Qt version: 5.15.8
Architecture: x86-64
Graphics platform: X11
Kernel version: 5.15.94-un-def-alt1

Steps:

1. Run from console: $ qcad
2. Reduce the size of the program window.

OBSERVED RESULT: Label overlay.

EXPECTED RESULT: Correct display of inscriptions (text in the bottom panel).

Same behavior: on first run.

Reported in forum 2 times:
https://www.qcad.org/rsforum/viewtopic.php?f=95&t=9887&p=40202&hilit=bugtracker#p40202 https://www.qcad.org/rsforum/viewtopic.php?f=33&t=9916&p=40298#p40298

Most likely the issue exist since QCAD Vers. < 3.25.2.0 (3.25.2)

A block with attributes inserted into Model_Space can’t be made completely invisible with the invisible switch (Eye icon) in the block list. It works for entities but not on attributes.

Andrew,

Deleting a node of a polyline (OD) followed by Undo (OO) while OD is still in ChoosingNode state and then deleting another node returns a polyline where both nodes are removed.

this.polylineEntity is set once in pickEntity() altered after pickCoordinate() and a clone is returned to the drawing.
The next pickCoordinate() continues with altering this.polylineEntity without retrieving the current form and is thus unaware that the former action might be undone.

The work around to undo a removal is first to terminate (QQ) PolylineDeleteNode then Undo (OO) and then start over with selecting the polyline and indicating nodes.

While adding nodes (OA) we can simply undo the last action and continue adding nodes.

Because the new entity has the same id as the initially one ...
... It should be possible to re-retrieve the actual entity by id in pickCoordinate() or deleteNode().

Regards,
CVH

Andrew,

Discovered in writing a custom tool:
hatchEntity.setCustomProperty(”MijnEPB”, “Ruimte”, roomData.numberText);
Works perfectly and I can retrieve the room numbers of all semi-automatically placed hatches in this instance of QCAD.

But I can not store and reload this file with these custom properties to use them in a new QCAD session.
I then assume the title must be ‘QCAD’.
Then I wonder how QCAD handles custom properties by other CAD applications.
Are they also removed on loading/writing?

QCAD doesn’t list these custom properties in the Property Editor.
Here hidden was fine unless they are not stored with the document.

Is it even possible to store them in the drawing file?
Why is the title a required variable when it can’t differ from ‘QCAD’?
Would it be possible to list them up in the Property Editor because I know they are filtered on title ‘QCAD’.

For now I revert to:
hatchEntity.setCustomProperty(”QCAD”, “EPB-Ruimte”, roomData.numberText);
Similar as the CAM tool that uses ‘Cam....’ for all keys.

Regards,
CVH

Andrew,

In some cases Draw > Ellipse > Inscribed in Quadrilateral (EQ) may return a perfectly healthy result but rotated for 90 degrees.
- Size doesn’t matter.
- Quadrant doesn’t matter.
- Geometrical open or closed base shape doesn’t matter.
- A mirrored base shape usually preforms well.

See attachment with examples.
The incorrect results (red) are rotated 90 degrees around the ellipse center (dotted)
Green is a correct result from a mirrored base shape.

Regards,
CVH

On macOS 14.1 and QCAD 3.28.2, the state of the OS (light or dark theme) affects some of the QCAD colour palette for the life of the session. So far I’ve noticed the problem with the keyboard shortcuts in tooltips and text in the command line output, but there may be other instances of the problem.

To reproduce:

1. Set the OS to light mode.

2. Start QCAD. Note the keyboard shortcuts in the tooltips are optimised for a light palette.

3. With QCAD still running, switch the OS to dark mode.

4. Note that while most of the QCAD interface switches to a dark mode palette, the keyboard shortcuts in the tooltips do not.

A similar behaviour is observed when starting from dark mode and switching to light mode.

I hope that makes sense. See attached screenshots for examples.

MacOS Sonoma, 14.1.1. MBP M1. / 3.28.2

When using SV / RO commands and using the checkbox to ‘use the mouse’ for scaling / rotating, then that setting is not retained at the next use. So every time the command is executed, a mouse move to check the box must be performed.

Andrew,

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

From the looks of it the cursor image data is read at a wider pace as it is stored.
One can distinguish the double cross positioning QCAD cursor but it is shifted.

Regards,
CVH

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

Andrew,

It seems that Attribute Definitions are created by default with Invisible = Yes
I can’t control this property on creation.
I can select the newly created Attribute Definition and toggle the flag.

Consequence when not updating this flag for each new Attribute Definition is that inserted Block Attributes disappear on synchronizing.
See attached files.

The default Invisible = Yes setting is not retained on save/reload.
(You will probably discover these flags to be ‘No’ in the attached files)
Synchronizing after a reload has no longer the mentioned consequence.

On inserting a Block Reference based on a Block with Attribute Definitions the Invisible flag of new Block Attributes is always ‘No’.
InsertBlock.js nor InsertBlockItem.js consider the Attribute Definition Invisible flag status when creating and inserting a new RAttributeEntity object.
e.g.: InsertBlock.js L184-L206

IMHO:
- Invisible = Yes on creation is not the best default for new Attribute Definitions.
- Not retaining this flag on save/reload is probably not intended.
- Disregarding the Attribute Definitions Invisible flag on block insertion seems incorrect.

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

Regards,
CVH

This can be done as is in QCAD today, but a quick convenience UI bit would be much appreciated.

Suppose you are working off a bitmap image (transcribing old scan, or you got your apartment’s floor plan like this, because, uh, what tenant needs DXF). It has dimensions markers and everything, but fat chance it’ll be to actual CAD scale after importing.

So, to bring it to scale, you measure between two tick marks on the scale, compute ratio based on measurement and what’s written on the dimension line, and do a scale operation (you can also have QCAD compute the ratio by using math expression, whatever).

That works fine.

A purely just for convenience function to do that would be much appreciated: pick two points, enter what the actual distance between them is, poof bam, appropriate scaling operation is applied.

As a twist, there could be some other bitmap skewing options, like “the points I’ve selected are on a horizontal/vertical line/at an angle of X degrees, then the bitmap would also be applied this transform.

Hello,

I’m unsing a two display environment and got all Tools and Widgets placed on the second display.
See qcad1.png

There are two problems:

1.) When I open another application on second display, three toolboxes stay on top, the others are behind new application.
See qcad2.png

2.) When I minimize Qcad only the mainwindow will be minimuzed, all the toolboxes and widgets stay on second display also with problem 1.
See qcad3.png

Whould be great, when this issues will be fixed

Thank you very much
Andreas

P.S.: Hope described well, if not, please drop me a reply...

 FS#1604  was issued because of non-intuitive hierarchy of the preferences for the Explode function.
The task comment recieved explains the funcionallity in details not found elsewhere.

Indentation of the phrase ‘Spline Segments:’ suggest hierarchy.
Graying out the drop down box for the number of spline segments establish hierarchy.

Hi,

I have a drawing where I use text with superscript. In this case when I use autozoom, it does not work as I expect. It includes the 0,0 coordinates too. The problem also occures when I export the drawing into svg.

I attached an example, just use the autozoom.

Thanks,
Soma

Win 7 32 bit QCAD 3.20.1

Ofsset of a base-line with arcs results in massive ammount of errors.
Most of them occur as a cluster of very tiny segments and are part of the offset. (zoom far in at the red circles)
Mostly they occur where the offsetted arcs should merely be trimmend pairwise.
Some occur as detached entities or as detached strings of entities very near the offset (strings not documented).
Spooks occur at opposite site when base-line is not closed.
360° curls can occur with R = Offset.
Null-entities may occur (not documented, hard to find and not able to copy).

The base-line is checked and sound and has mixed tangentially or not tangentially connected arcs.
Offsetting the mother base-line of the base in the file has similar effect but not all and/or different ones.
Also encountered with offseting polys from fonts.
Used to define pocket paths for CNC.
Detected because the CNC driver will not accept Self-crossers, Null-entities or open ends depending on the settings.

Work arround is to explode and select small entities but this does not solves the issues.
1) Choosing the tolerance large enough will detect small segments that should stay.
2) Recombining will generate new ones at the place where the main segments remain crossed.
Cleaning up the paths is a daunting process with some thousand segments for several offsets.

I assume this has an infuence on the CAM part of QCAD too unless the offset method is different.

QCADpro 3.25.2.1 / win7pro 32 bit / 4GB / 1e generation i7 2.6Ghz / HDD GeForce GT 520

The method PE casts the clipboard on individual hatch segments.
Hatches should be considered as a single complex entity not allowing certain actions.

Discovered while:
https://qcad.org/rsforum/viewtopic.php?f=33&p=30008#p30008

Not that it matters: In doing so the scaling is off too.

Regards,
CVH

From this Topic:
https://www.qcad.org/rsforum/viewtopic.php?f=33&t=7818

Trial 1 doesn’t gives the intended result.
Trial 2 includes manual altering back and forth the Format field what gives the intended result

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

With the attached file:
Viewing Layout1
Changing ON/OFF or Frozen state of layers in the Layer List

The view doesn’t update immediate.
Selecting an entity: Yes
After QQ Yes
Switching to another Application and reverting the focus back to QCAD: Yes
Using zoom / pan or the Zoom functions: No
Changing the display modes: Yes
Starting an action: No

That would ease this task:
https://www.qcad.org/rsforum/viewtopic.php?f=32&t=8000

Correct surface area included.
CVH

QCAD Professional
Win7 installer 32 bit
Version: 3.25.2.13 (3.25.2.13)
Internet: QCAD.org
Build Date: Feb 12 2021
Revision: cad2d36
Qt Version: 5.13.2
Architecture: i386
Compiler: Unknown

In the file provided one would expect *VARIES* in the property editor under custom properties when selecting 2 or more entities.
The key list is reduced to what keys are common to the multiple selection. (Here 3)
The values displayed are inconsistent depending the selection.

Select All » 3 custom properties of line 3
Select the 3 vertical » 3 custom properties of line 2
Select the first vertical and the diagonal » 3 custom properties of line 1
Select all but the first vertical » 3 custom properties of line 3
And so on ...

Regards,
CVH

When I use poly.appendVertex(vector, bulge) the polyline is finally created with NAN widths

This, while the signature explains that bulge, width1 and width2 default to zero.
https://www.qcad.org/doc/qcad/latest/developer/class_r_polyline_entity.html#a9ee706e50d6cc267fc84a85b7c81d5e6

Regards,
CVH

Andrew,

Reading:
https://www.qcad.org/rsforum/viewtopic.php?&t=8286

Can you update addSimpleText() as Text.Width is fixed =100

What is the noTextWidth value?

As far as I can detect ...
PrintPreviewImplPro.prototype.addDecorations uses value 1.
CrankWheel.js uses value 1.
ExText.prototype.beginEvent uses value 2.
ExDrawFonts.prototype.beginEvent uses value 1.
Counter.prototype.getOperation uses QCAD.ini or default zero.
TextAlong.prototype.getTextData usses the width of the textData from the dialog.

Regards,
CVH