Flyspray:: Flyspray::QCAD: Recently opened tasks 2014-07-23T19:55:25Z FS#1077: Centreline Cross using wrong Coordinate Format 2014-07-23T19:55:25Z 2014-07-23T19:55:25Z

My Coordinate Format/Decimal Point is adjusted to Dot’.’ but the “Centreline Cross (C,S)” will only accept Comma for Angel. X/Y works fine!

BTW: Is the spelling correct in the Menu? Should it be spelled “Centerline Cross” instead of “Centreline Cross” ...?

FS#1076: Minimally reproducible crash of v.3.6.2 on Mac OS X 10.9.4 when editing any text object. 2014-07-22T21:53:59Z 2014-07-22T21:53:59Z


I have just updated my Mac OS from 10.9.2 to 10.9.4. QCAD 3.6.2 seems to be working normally under the newest version of Mac OS, but has developed a very specific bug which leads to reproducible crashes when a text object is edited.

Steps to minimally reproduce:
1. Open QCAD
2. Create a text object
3. Place the text object on the canvas
4. double-click the text object and edit its contents
5. click OK to accept changes
6. repeat from step 4 three or four times.

After several attempts to edit a text object, QCAD will crash with EXC_BAD_ACCESS (SIGBUS) in thread 0 (QCoreApplication).
The crash can also be triggered by moving the text object around on the canvas (instead of editing its contents).
The bug does not require anything else (no other objects on the canvas, no particular font, occurs in both new and previously saved documents).

Apart from this bug, QCAD seems to work fine on OS X 10.9. The text editing crash did not occur before the latest OS update. No other applications on my system seem to be having any problems. If this problem can be fixed, I think QCAD will be quite usable on 10.9.

Daniel Duke
FS#1075: dwg2svg: include path broken 2014-07-21T14:14:18Z 2014-07-21T14:09:28Z


FS#1074: Application Preferences: dimension font 2014-07-15T21:45:17Z 2014-07-15T21:45:17Z

Dimension font setting as default for new drawings has no effect.

FS#1073: Duplicate images with same path not saved 2014-07-14T09:45:36Z 2014-07-14T09:44:33Z

Only affects files saved through dxflib.

FS#1072: Resolve Relative paths on command line 2014-07-07T17:36:35Z 2014-07-07T17:36:35Z

I have aliased qcad to run it from terminal. There is a small glitch when opening a file from a different location using relative path names:

$ alias qcad
alias qcad='/opt/qcad-3.6.0-pro-linux-x86_64/qcad'

$ cd /a
$ qcad some.dwg &
$ cd /b
$ qcad other.dwg

Import Error is shown:
> Can't open file
> /a/other.dwg.
> File is empty.

$ qcad /b/other.dwg # absolute path works

$ readlink /proc/pid-of-qcad/cwd

Qcad somewhere stores the path, from where it is first launched. The next “launch” will not use the next location but refer to the first one when constructing the full path name of the file name in the argument.

Maybe that can be easily improved (the message is wrong too).

FS#1071: (Bitmap) scaling convenience option 2014-07-04T12:16:09Z 2014-07-04T12:16:09Z

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.

FS#1070: Add support for trace entities 2014-07-02T13:26:11Z 2014-07-01T12:09:20Z

See forum thread at:

FS#1069: Hatching uses current 'point' display - results in wrong hatching 2014-07-01T10:33:48Z 2014-07-01T10:33:48Z

If a chosen hatch contains points, the hatch will use the point display set in the Application/Current drawing preferences, this leads to incorrectness with certain hatches.

In my attached example I have used AR-CONC (Concrete), the result is something which is wrong!

FS#1068: Isometric bitmap 2014-06-23T07:58:18Z 2014-06-23T07:58:18Z

It would be a nice feature to be able to create an isometric projection of a bitmap.

Christian Aigner