Flyspray:: Flyspray::QCAD Bugtracker: Recently opened tasks https://qcad.org/bugtracker/ 2019-06-24T09:54:41Z FS#1907: having issues importing and opening dxf files 2019-06-24T08:14:02Z 2019-06-23T20:28:36Z

can not import dxf files

jerry buck https://qcad.org/bugtracker/:1907
FS#1906: Draw > Polyline > Polyline from Segments: Converting full arcs to polylines 2019-06-24T09:54:41Z 2019-06-22T12:02:01Z

Win7/32bit
QCADpro 3.22.1.0

Full 360 degrees Arcs don’t convert correct to polylines with the methods OG and OC.
Both methods create a zero-length open type Polyline and remove the full Arc.
OG creates a Poly with 2 vertexes at the startpoint (= endpoint) and OC one with 0 (zero!) vertexes.
The firts one is selectable, the second one only with ‘Select All’//TA because there are no references.

The OL method with the same start and endpoint doens’t affect the full arc.
Neither a poly is created nor an error is generated that the method failed.

Typical the bulge of the OG method is (-)16331239353195370, the OC method has no references.
The math to calculate the bulge should result in a division by zero or an illegal function as tan(π/2).
Therefore a polyline can’t contain a 360 degrees arc by standard means.

From the OC method is known that it simplify coradial arc strings to a single arc.
This should not result in 360 degrees arcs what would result in zero-length segments.
(With CAM fuzzy things may happen at such positions)

Simplifying coradial arcs strings that would create a 360 degrees arc should result in no less then two coradial Arcs.
The OG method will then creates a open Poly with 3 vertexes, OC a closed one with 2 vertexes.

Found while fiddling around with editing CXF fonts.
CXF uses full Arcs, two half arcs and even polylines with coradial segments that forms circles are supported,
the OC closed polyline with 2 vertexes is recoded as two 180 degree Arcs (90-270&270-90).

Regards
CVH

CVH https://qcad.org/bugtracker/:1906
FS#1905: View > Property Editor: Changing attribute of block changes order of attributes 2019-06-19T19:44:16Z 2019-06-19T19:44:16Z

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

Andrew https://qcad.org/bugtracker/:1905
FS#1904: File > Bitmap Export: Non-plottable layers not exported 2019-06-17T17:24:13Z 2019-06-17T17:20:57Z

File > Bitmap Export does not export non-plottable layers.

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

Andrew https://qcad.org/bugtracker/:1904
FS#1903: Saving layer settings, e.g. visibility status, associated with a view 2019-06-13T22:08:44Z 2019-06-13T22:08:44Z

In a medium complex drawing it may be too much details to have all layers in a drawing visible at once.

Instead a number of views would be created that saves not only zoom level and position but also what layers are visible and not (as appropriate for the purpose of that particular view). This is very cumbersome (to the extent it is not really realistic) to achieve today and requires a lot of duplication of both model and layers.

The advantage of adding this is the ability to have only one model (with multiple views) and avoid duplication of work and the risk of inconsistency inherent with many copies of the model.

As a further (and natural extension to this) would be the ability to used this functionality with view-ports to be able to create (possibly many) paper-spaces from a single model. This would however require view-ports to be aware of what view they are a window into. A single change in the model would then propagate to all defined view-ports and paper-spaces.

Johan Persson https://qcad.org/bugtracker/:1903
FS#1902: CAM G-Block Toolpath 2019-06-13T08:59:43Z 2019-06-13T08:56:58Z

Hallo Andrew,

Still busy on the never ending G-code story. Urgently needed the very handy G-code Block Toolpath. This ‘toolpath’ also solves a lot of “editing requests”.

H. Stiekema https://qcad.org/bugtracker/:1902
FS#1901: CAM Traverse Toolpath 2019-06-13T08:59:25Z 2019-06-13T08:53:49Z

Hallo Andrew,

Still busy on the never ending G-code story. Urgently needed the very common Traverse Toolpath.

Example added as pdf.

Greetings

H. Stiekema https://qcad.org/bugtracker/:1901
FS#1900: Remote shares initially not accessible. 2019-06-12T08:20:23Z 2019-06-12T08:10:27Z

My data files are stored on network shares (synology) with a GB link. QCAD Pro is run in Admin mode.

While in my Windows browser all remote shares are accessible (Green), in the QCAD file open menu they are initially shown as not accessible (Red). By accessing a specific drawing file in a remote share, the share will open and turn green.

Same behavior using ‘Open recent’. Always the message is given that the requested file does not exist, and the file is wiped from the ‘Recent Open’ list. Only if the share is first accessed through ‘Open’ with a random file, it will turn and a ‘recent open’ file for that share will open.

Drag and Drop from a remote share will never work.

Robert Boers https://qcad.org/bugtracker/:1900
FS#1899: View > Auto zoom: zoom to invisible entities in blocks 2019-06-10T08:39:33Z 2019-06-10T08:15:57Z

Create and insert a block with entities on layer “0” and layer “1”.

Switch off layer “1”.

Auto zoom zooms to block boundary of all entities, including those on layer “1”.

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

Andrew https://qcad.org/bugtracker/:1899
FS#1898: Lines are broken when saved in layers. 2019-06-10T07:39:58Z 2019-06-10T00:02:01Z

QCAD community edition.

I use this program to generate CAM data. Whenever I save a the same text in different layers - one of the layers saved has broken lines. I have to spend hours extending and trimming each segment to reattach them.

Duplicate problem:

New file
Add some text
Explode into lines
Add layer
Add same text to same location on new layer
Explode into lines
Save file

Dean Moe https://qcad.org/bugtracker/:1898