Roadmap for version Post 3.0 Expand all | Collapse all

25% of 34 tasks completed. 26 open tasks:

FS#11 - File: SVG Export Expand Collapse

Open

ExporterPG (preserve geometry)
- Texts are exported as text tags, with 'similar' font
text
- other formatting
  - exporter for presentation (based on paths): implemented
  - ExporterPG: TODO

Postponed

Global Preferences:
- Number of generated segments for ellipses [postponed]
  - Problem: exported SVG files can be very large under certain circumstances
ExporterPG
- Export layer information if possible / maybe group by layer [postponed]

Done

hatches
- solid fill
- pattern
text
- line breaks
  - ExporterPG: Since line spacing is rendered differently in SVG, the used text space might be different, too.
- position broken for some texts

FS#12 - File Export Formats Expand Collapse

Open

Postponed

SQL [postponed]
Flash (library: swf) [postponed]
DGN [postponed]
Google SketchUp [postponed]

Done

FS#17 - RLineEntityPointer doesn't work as function argument of type REn Expand Collapse

Script code (SvgExporter.js):

245 // only export entities on main block "*Model_Space":
246 if (realEntity.getBlockId() == this.doc.getBlockId("*Model_Space")) {
247   RFileExporterAdapter.prototype.exportEntity.call(this, entity, false);
248 }

Script debugger exception:

Uncaught exception at /home/martin/workspace/rsframework/scripts/File/SvgExport/SvgExporter.js:246:
Error: :-1:-1: RExporter: Argument 0 is not of type REntity*.
<native>(RLineEntityPointer(0xb6fb158), false) at -1
<anonymous>(entity = RLineEntityPointer(0xb6fb158), preview = false) at
/home/martin/workspace/rsframework/scripts/File/SvgExport/SvgExporter.js:246
<anonymous>() at /home/martin/workspace/rsframework/scripts/File/SvgExport/SvgExporter.js:211

Workaround: Used exportEntity() with ID as argument instead. However there may be other cases where no alternative method is available.

RFileExporterAdapter.prototype.exportEntity.call(this, realEntity.getId());

FS#21 - Add line weight scale factor Expand Collapse

Required for extreme units such as Nanometers or Kilometers. See also FS#20

FS#70 - 64bit Expand Collapse

ECMAScript engine (garbage collector) crashes on Mac OS X and Linux 64bit if QCAD binary is compiled as a 64bit binary.

FS#117 - Use APPID when handling extended entity data to prevent dataloss Expand Collapse

Rationale:

Let QCAD handle extended entity data, that is used in the industry to instruct postprocessing applications, e.g. the tooling of a mill or robot.

When I say group code or specs below, I refer to this document http://www.autodesk.com/techpubs/autocad/acad2000/dxf/extended_data_dxf_ab.htm

Current:

In the property editor I can add key value pairs to drawing entities. As in this script:

entity.setProperty(new RPropertyTypeId("MY_KEY"), "MY_VAL");
entity.setProperty(new RPropertyTypeId("MY_REAL"), 123);

In DXF this results in a group code "QCAD" followed by alternating keys and values as strings and typed positions respectively:

[…]
  0
LINE
[…]
1001
QCAD
1000
MY_KEY
1000
MY_VAL
1000
MY_REAL
1040
123.0
[…]

Expected:

From reading the specs, this looks perfectly valid. I'd say though, that QCAD is not right to expect any extended data to follow this pattern. The extended entity data, that I want to recreate eg, looks like this:

[…]
  0
LINE
[…]
1001
MY_DATA
1000
MY_FOO: some text
1000
MY_BAR: 1.250000
[…]

That is: a group code, followed by some string values. Notice that the (limited) typing facilities mentioned in the spec are not used, but the application relies on its own peculiar parsing. The same group code appears in the head of the document as an APPID:

[…]
  0
APPID
  2
MY_DATA
 70
     0
  0
[…]

Proposed:

I suggest, that QCAD uses APPIDs to group extended data. Otherwise data loss may occur. In order to not have to maintain a table of known APPIDs, that tells how to parse their extended data, I further suggest that QCAD not expect extended data to follow a "key value" pattern but an "APPID entries" pattern. Here too data would be lost, if there was an odd number of entries in the extended table and QCAD insisted on its own approach.

Within the specs, deep trees could be constructed with the use of the control string (code 1002, { and }), and the propertyEditor would become a nightmare;) So I propose, that QCAD might parse only extended data with its own APPID in key value pairs, and data with other APPIDs as just an ordered list of entries. (In ECMAscript an array will have to be used, as object properties do not keep sequence.)

FS#137 - SVG Export precision Expand Collapse

In files exported with the (even PG) exporter I sometimes see values like these: 334.99999999999994 or 570.0000000000001 and very often 12 digits of precision.

To safe on file size, I suggest, that QCAD rounds values on SVG export to eg. three places. When viewed in an ordinary web browser, that will result in a precision of 1 inch / 96dpi / 1000 = 0.00026mm, not? Ends should still meet.

FS#154 - Image: move reference points to scale Expand Collapse

Image: move reference points to scale

FS#173 - explode text to letters Expand Collapse

implement

FS#264 - Support of "Layouts" (paper space) Expand Collapse

There is one important ACAD feature that I would really like to see supported in QCAD3 and that is "Layouts"

Looking at the block lists, it seems to me that it can't be too much extra work to support it, since the model space and different paper spaces are already shown there - and one can edit it.

QCAD draws infinitely easier than ACAD and drawing layouts is a primary feature of ACAD. With this in QCAD I can hardly see why anyone that does 2D work would need ACAD at all.

FS#265 - Block Attributes Expand Collapse

Defining block attributes
Editing block attributes
(DDATTE, ATTEDIT, ATTDEF)

FS#268 - Define grid origin Expand Collapse

Define grid origin

FS#281 - dxf import: show paper space by default Expand Collapse

dxf import: show paper space by default if whole drawing is constructed on paper space or read 'current block' from sxf if available.

FS#335 - Drawing preferences: Change font of dimensions Expand Collapse

Configure font used for dimensions.

FS#396 - Blocks: moving blocks: show bounding box Expand Collapse

Blocks: moving complex blocks with drag and drop should show bounding box as preview

FS#454 - combined move/rotate/scale with two reference points Expand Collapse

It would be extremely helpful, if marked objects could be moved/rotated/scaled in a single step with two reference points as source and two reference poitns as destination. With a tool like this, "should match"-drawings could be merged easily.

FS#455 - logical operations for polylines Expand Collapse

A missing feature in my work are logical operations (combine, intersect, ..) for polylines

Example:
Draw some elements, select them, say combine. The result will be the outline of all elements.

FS#467 - Feature request for new Arc tool option to add to Arc set Expand Collapse

For and behalf of mandrena

To add another Arc tool option in Arc tools set:

1.Specify Start point for Arc.
2.Specify End point for Arc.
3.Specify "Tangent" direction (without being restricted in input field) so you can visually select a point on your desired Tangent line!

FS#477 - crop objects at page margins Expand Collapse

It would be nice if QCad would print only objects inside page margins (i.e. to print a detail of a large drawing with margins). At the moment objects are visible up to page borders, and exporting to PDF with re-printing to a larger page contains even more objects.

FS#482 - Block with hatch, scaled with different X / Y factors Expand Collapse

Block with hatch scaled with factor in X different from factor in Y leads to problems if contour contains arcs (which cannot / are not scaled disproportionally).

FS#496 - Error in Application Preferences -> Default Dimension Settings Expand Collapse

In the Application Preferences (but also in the Drawings Preferences) → Dimension → Default Dimension Settings → Label Format → Linear (and Angular) Dimension → Show Trailing Zeros, the example is wrong if the option is checked.

FS#498 - issue importing from Autocad Expand Collapse

There is an issue importing from Autocad:
lines and quotes (both arrows and text) appear too much big (see attachment).
I can fix quotes modifying dimensions in "current drawing preferences", but lines are still too thick.
Autocad's dxf are opened with right line thickness but wrong quotes.
Furthermore, Autocad opens Qcad's dxf files showing wrong quotes.

FS#500 - Autohide Side Panel Expand Collapse

it would be ideal to be able to have the option to autohide the side panel to increase the visible drawing space when working on a small screen.

FS#502 - Points on line: enter distance instead of number of points Expand Collapse

Points on line: enter distance instead of number of points as a variant of the tool or as a new tool.

FS#503 - Convert entities to points with a fixed distance Expand Collapse

Select lines, arcs, ... and convert them to points along the lines, arcs, ... with a fixed distance.

FS#508 - zoom speed option Expand Collapse

Add a zoom speed option in preferences

Roadmap for version 3.1.0

100% of 1 tasks completed.

Text Version