QCAD Bugtracker

Add support for scale transforms in SVG import.

Original report:

When importing an SVG created with Inkscape, one of the elements (rectangle) is shifted (mirrored?) to the left.
The example (back.svg) is appended. If you open it with Inkscape, you see the rectangle should be above the “USB” label.

My impression is that the sign of the X coordinate is swapped for some reason. At least if I mirror it
using two points on the Y axis, it seems to appear where it should be.

Apart from this, also the dimensions are wrong after import. In the original SVG, the outer shape is 144.3mm wide.
This is also visible in the header of the SVG:

 width="144.300mm"
 height="53.800mm"

However, after importing to QCad, the width is measured as 40.7247. This is a puzzling factor of 3.5433 which doesn’t look
like metric/imperial conversion issue but like a complete misinterpretation of the sizes/units used in the SVG.

Add support for importing units other than defaults (pixels) based on unit given in svg:width / svg:height attributes.

QCAD seems either to mishandle or ignore svg group transformations altogether.

Importing the attached file into QCAD renders the largest polygon (polygon18) to be rotated and misplaced. This is shown in actual.png. The expected result (original Inkscape renedering) is shown in expected.png.

Looking at the code of the original drawing it can be observed there is a transformation applied to the group which polygon18 is in:

 <g
   style="stroke-width:0.35433099;stroke-miterlimit:4;stroke-dasharray:none"
   id="g20"
   transform="rotate(-90,316.66796,298.95141)" >
   <path
      inkscape:connector-curvature="0"
      id="polygon18"
      d="..." />

Removing the ‘transform’ attribute produces virtually identical (erroneous) rendering in Inkscape as well.

The attached file should result in two overlapping circles, it does not, it results in a single ellipse.

The “<circle ... />” directive seems just be ignored in this case, but in other instances I have seen it result in ellipses.

And the “<ellipse ... />” directive should of course result in a circle, when rx and ry are the same.

(I’m running on FreeBSD, but that was not an option in the selection for Operating System)

When importing a SVG file in version 3.7.5, it qcad turns polylines into polygons.

I’m attaching a trivial .SVG file showing this, it should *not* render as a rectangle,
but as a “rectangular upper case C”.

And many thanks for making good quality CAD software available to the FOSS community.

I noticed, that paths are not fully imported into QCAD. I rewrote case “m” of “SvgImporter” like below, that way also straight line segments are drawn correctly. Case “M” should be similar:

      case 'm':
          x = ox = coords[0];
          y = oy = coords[1];
          x0 = x;
          y0 = y;
          for (k=2; k<coords.length; k+=2) {
              x += coords[k+0];
              y += coords[k+1];
              this.importLine(ox, oy, x, y);
              ox = x;
              oy = y;
          }
          break;

Complete SvgImporter.js and SvgImport.js

1. Implement SvgImporter.prototype.importFile to import the SVG file with the given fileName. Reading only all path data without any attributes or transformations is fine as a first step. SvgImporter.prototype.importFile() currently imports one hard coded path data as proof of concept.
2. Implement SvgImport.prototype.beginEvent() to show a file open dialog that lets the user choose an SVG file to import.
3. Support SVG as file format for part library items through SvgImporter

This should be enough to import any SVG file in library/symbols

Attached sample drawing, that kills QCAD 3.1 beta when exporting to SVG.

The crash happens in line 38 of SvgExporterPG in function SvgExporterPG.prototype.exportPolyline

var pp = new RPainterPath(polyline.toPainterPath());

Somewhere in the 3.1 series the SVG exporter (both precise and PG) started to make lines that are zero (0) width in CAD 0.01 (@scale 1:1) points wide in exported files (0.1 @scale 1:10). I use such lines to constrain exported files to a common size and rather not have them show. In my view, this is a regression, as there is no reason for changing line weight, isnt it? If I wanted the lines to have weight, I’d draw them with a weight.

Hi,

when I export a dxf draw to svg the text objects shows in a bit different place.

QCAD version is 3.21.3.14

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.

When exporting a drawing to SVG, polygons containing arcs (trimmed circles in this case) are converted to straight lines. If the polygon is exploded first, then it exports correctly. Of course, this isn’t useful if closed polygons are required for the program using the SVG file. Solid hatch fills export correctly. See attached DXF and corresponding SVG export.

https://qcad.org/rsforum/viewtopic.php?f=33&t=9731

Quick SVG export of a block reference can lead to unexpected results if the vertical flip option is enabled during the insertion of the block. See above forum thread.

Both SvgExporters ignore the exportPoints setting. Attached patch takes care of that. To be applied from within the “scripts” directory.

Nitpicking in File/SvgExport/SvgExport.js, var properties is meant to be a plain Object instead of an Array, isn’t it?

The SvgExporter opens a “group” for some entities, but never closes that group. The resulting nesting can get quite deep and does not conform to the original. I tentatively patched the script as below:

--- SvgExporter.js-orig	2011-05-23 10:55:17.239998578 +0200
+++ SvgExporter.js	2011-05-23 10:55:17.239998578 +0200
@@ -226,6 +226,11 @@
 //        RFileExporterAdapter.prototype.exportEntity.call(this, this.realEntity
 //                .data(), false);
 //    }
+    
+    // dimensions and block references are grouped, close the group tag here
+    if (isDimension(entity) || isBlockReferenceEntity(entity)) {
+        this.writeEndElement();
+    }
 };
 
 SvgExporter.prototype.endEntity = function() {

There might be a better way, but that is what I came up with on short notice.

Quick SVG Export suggests file name “Untitled 1 [*].svg”

Remove [*] (comes from window title).

If I understand correctly, SVG export uses svg groups to keep QCAD block entities. This in itself is very useful. There is no way to correctly keep layer information, as QCAD blocks can contain elements on different layers, while SVG only knows about groups. That is a deficiency of SVG.

To save on file size, there was some potential to get rid of ever repeating same attributes on entities, eg: style=”stroke:#000000;stroke-width:0.25;stroke-dasharray:2.16,1.08”

To optimize “By Block” is easy: just set the attribute on the SVG group, and omit on below entities styled “By Block”.

To optimize “By Layer” is a little more involved, but might be solved by using css:
- Create a class by the name of the Layer
- add the class attribute to elements styled “By Layer”

Then only individually styled entities would get a style attribute, and filesize of SVG could be halved in most cases.

This just an idea :) Having written this, I now realize, that QCAD can style weight, pattern, color each extra, so the optimazition could only be applied to entities, where everything is “By Layer” or “By Block”. But that should be the case most of the time.

SvgExporter.js uses PrintPreview to parse the scale string, and therefore depends on the qt GUI part. That should not make maintenance harder to call RMath directly there? Results seem to match from a first look.

--- SvgExporter.js~	2011-10-20 14:11:45.527589416 +0200
+++ SvgExporter.js	2011-10-20 14:12:46.277502814 +0200
@@ -1,6 +1,5 @@
 include("scripts/library.js");
 include("scripts/date.js");
-include("scripts/File/PrintPreview/Print.js");
 
 /**
  * File exporter implementation for the SVG format.
@@ -116,7 +115,7 @@
     this.svgUnitAbbr = ret[1];
 
     // scale
-    this.scale = Print.parseScale(this.scaleStr);
+    this.scale = RMath.parseScale(this.scaleStr);
 
     var bb = this.doc.getBoundingBox();
     var size = bb.getSize();

Points in hatch patterns are exported as empty path elements in the exported SVG.
Therefore, the hatch patterns “DOTS” and “AR-SAND” are not visible in the exported SVG.

• during the start up
• last info from splash screen: LibraryBrowser: Directory: metric

./qcad: line 5:  2321 Segmentation fault      (core dumped)
LD_LIBRARY_PATH=/home/martin/opt/qcad-3.0.0-tp1-prof-linux /home/martin/opt/qcad-3.0.0-tp1-prof-linux/qcad-bin $*

(gdb) bt
#0  0x03180194 in __strncmp_ssse3 () from /lib/libc.so.6
#1  0x08c7741e in __xmlParserInputBufferCreateFilename ()
#2  0x04333e04 in xmlParserInputBufferCreateFilename ()
   from /usr/lib/libxml2.so.2
#3  0x043bc9c0 in xmlNewTextReaderFilename () from /usr/lib/libxml2.so.2
#4  0x041fde98 in ?? () from /usr/lib/libgnomevfs-2.so.0
#5  0x041fe381 in gnome_vfs_mime_get_value () from /usr/lib/libgnomevfs-2.so.0
#6  0x041fbb38 in gnome_vfs_mime_get_icon () from /usr/lib/libgnomevfs-2.so.0
#7  0x040d0ab6 in gnome_icon_lookup () from /usr/lib/libgnomeui-2.so.0
#8  0x040d1037 in gnome_icon_lookup_sync () from /usr/lib/libgnomeui-2.so.0
#9  0x0240ee92 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#10 0x026a0658 in QFileIconProvider::icon(QFileInfo const&) const ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#11 0x025cd467 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#12 0x025c2f89 in ?? ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#13 0x025c3ba4 in QFileSystemModel::index(QString const&, int) const ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#14 0x025c7289 in QFileSystemModel::sort(int, Qt::SortOrder) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#15 0x025bc86c in ?? ()
---Type <return> to continue, or q <return> to quit---
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#16 0x025c6d68 in QFileSystemModel::qt_metacall(QMetaObject::Call, int, void**)
    () from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtGui.so.4
#17 0x08881dc2 in RFileSystemModel::qt_metacall(QMetaObject::Call, int, void**)
    ()
#18 0x02cd3c83 in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#19 0x02cdede6 in QMetaCallEvent::placeMetaCall(QObject*) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#20 0x02ce09a0 in QObject::event(QEvent*) ()
   from /home/martin/opt/qcad-3.0.0-tp1-prof-linux/libQtCore.so.4
#21 0x025c07c3 in QFileSystemModel::event(QEvent*) ()

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

Correct surface area included.
CVH

See RDwgEllipseImporter::import

It would be nice if the OS X Pro version could support the standard OS X full screen pattern in the same way as native OS X applications.

With this I mean that applications in full screen will create a temporary new desktop as long as they are in full screen mode.

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.

Support drawing linetype scale factor (LTSCALE)

E.g. if a block reference has its color set to ‘red’ and the block reference has an attribute with color=’ByBlock’, the attribute should be displayed in red.

I very much like the new middle mouse button zoom in/out and congratulate Andrew for implementing it so quickly but there’s an annoying delay that is necessary between successive zoom in/out actions. This is easily understood by comparing it to zooming in/out with the +/- keys. With the keyboard you can repeat zooms as quickly as the keyboard repeat rate allows; with the middle mouse button quick zooms are not possible.

Draw a horizontal dimension. Stretch (S S) it. The label remains in place. It should instead go to the new center. (Unless it was manually positioned perhaps...)

Workaround: Pick one extension and drop it to where it was, label gets centered.

Stretching hatch entities results in broken hatches.
Regression introduced in QCAD 3.1.5, bug still present in 3.2.2.

It would be nice if we could use the Stretch tool also on blocks.

There are so many possibility’s to build a really good (time-saving) block-list /library with preassembled parts but if I have always to explode / ruin the block to use the stretch tool doesn’t helps the productivity.

hello. if i use the tool on my own drawing, no problem, but on an element coming from the library, the blue selection square appears, it moves but the chosen shape doesn’t follow. i’ve tested several ways and even by creating a block. cordially

bonjour. si j’utilise l’outil sur mes propre dessin, aucun Souci, mais sur un élément de venant de la bibliothèque, le carre de sélection bleu apparait, ce déplace mais la forme choisi ne suis pas. j’ai teste plusieurs manière et même en créant un bloc. cordialement

The stretch function does not work at all. I tried it in the old version 2.2.2 where it worked.

Test case:

In Windows, set up say 2 or 3 new blank drawings.Then close them down one by one and notice the behavior when closing these drawing windows down!

Status change for Visibility is without any effect on Viewports in Paper_Space.

Case:
Entities drawn on a layer in Model_Space. Visibility on/off works.
Situation covered with a Viewport, placed in Paper_Space, Edit content launched for that Paper_Space, Visibility on/off doesn’t works.

It was properly working in previos QCAD versions ...

status bar: avoid scientific display of large float numbers

see also:
http://ribbonsoft.com/rsforum/viewtopic.php?t=1717

Please refer to topic: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=8921

- Launch QCAD-Pro 3.26.4.13, Status Bar is off by default
- Set menu View > Status Bar on
- The Status Bar is showed but the menu options remains unchecked
- Quit QCAD-Pro
- At launch QCAD-Pro opens with the Status Bar toggled off
- Set View > Status Bar on (or issue GS from command line)
- At the next launch the Status Bar is off

Note: the preference StatusBar in the .ini file has the value “false” when it should be “true”. Changing the value manually to “true” makes the Status Bar appear just for the next launch of QCAD then the preference is reset to “false” by QCAD.

- Deleted the .ini file, same behavior
- Changed user, same behavior
- Tried on MacOS 10.11.6 (El Capitan), same behavior

QCAD Professional

Version: 3.26.4.13 (3.26.4.13)
Internet: QCAD.org
Build Date: Nov 18 2021
Revision: fbb9f37
Qt Version: 5.10.1
Architecture: x86_64
Compiler: Clang 8.0.0

Riepilogo hardware:

Nome modello: iMac
Identificatore modello: iMac12,1
Nome processore: Intel Core i5
Velocità processore: 2,5 GHz Numero di processori: 1
Numero totale di Core: 4
Cache L2 (per Core): 256 KB
Cache L3: 6 MB Memoria: 16 GB Versione Boot ROM: 87.0.0.0.0
Versione SMC (sistema): 1.71f22

It could be very useful to have in the status bar area - input fields for typing in X and Y position, Distance and Angle etc...

For example these could be used instead of entering absolute/relative coordinates in the command line.

1.Draw line.
2.Start point - enter in X Field.
3.Next point - enter in Y Field.

This method could also be used for specifying positions when placing other entities.

For me I tend to use a combination of the command line/GUI for most work but I think for those who do not wish to use the command line this could be useful.

Startup preferences

On Mac 10.14.6: QCAD Pro → Preferences... → Startup

Check or uncheck “Enable Splash Screen”

1. Restart of QCAD, the splash screen with Initialising add-ons xx% is identical

2. Apply, Cancel and OK buttons - why have both Apply and OK buttons?

QCAD community, Git ba68e28d3d (current HEAD), fresh clean compile on Ubuntu 18.04/x64 (gcc 7.4.0, Qt 5.9.5)

QCAD version  3.23.0.2
Warning:  QApplication: invalid style override passed, ignoring it.
Warning:  Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication.
Warning:  action not found: "Scheme"
Warning:  RScriptHandlerEcma::eval: script engine exception:  "TypeError: Result of expression 'RS.getIdealThreadCount' [undefined] is not a function."
Warning:  "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
Warning:  RScriptHandlerEcma::eval: script engine exception:  "TypeError: Result of expression 'RS.getIdealThreadCount' [undefined] is not a function."
Warning:  "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
Warning:  At least one uncaught exception:
Warning:  "<anonymous>(uiFile = 'scripts/Widgets/ViewportWidget/ViewportWidgetQt.ui', graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:172\n<anonymous>(viewports = [object Object], uiFile = undefined, graphicsSceneClass = undefined) at /home/ice/w/qcad/qcad/scripts/Widgets/ViewportWidget/ViewportWidget.js:75\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:248\n<anonymous>() at /home/ice/w/qcad/qcad/scripts/File/OpenFile/../NewFile/NewFile.js:109\n<eval>() at 1\nslotTrigger() at -1\nopenFiles(args = , createNew = true) at scripts/autostart.js:209\nmain() at scripts/autostart.js:796\n<global>() at scripts/autostart.js:834"
17:14:39: Debug:    "<global>() at 172"

Then QCAD exits (does not start). As far as I remember, 3.23.0.2 release was fine.

Having a multi selection and at least one ‘older’ arc the startpoint indication in red of some entities might disappear.

Entities that suffer from this are:
Other arcs
Polyline
Splines

Only the ‘oldest’ arc in selection will have a startpoit indication.
Multi selection of ‘newer’ entities from the list above will not if an ‘older’ arc is part of the selection.
Deselecting de ‘older’ arcs will reveal the startpoints up to the ‘oldest’ arc.

In the file provided entities where drew in order from left to right.
Select all and start deseleting arcs from the left.

The behaviour is affected by changing the draw order property and a save/close/open.
In the second file the rightmost arc was set to draw order 7, the same as the 4th was.
After save/close/open it is renumbered to 8 and the behaviour is different as in the firts file.

Regards

Hi,

If you open an old qcad drawing thats DXF and edit text, the popup window shows “Main Font” as empty.

If you do not set the font and complete the edit, it will change the font from the standard to what looks like an Arial font.

If you set the font as “standard” during the edit, each time in future you open the editor it does at least have standard selected.

Ie if no font is specified in drawing, should it not select “standard”?

James

Using the move and scale tools, QCad sometimes (reason unknown so far) crashes in RC4 (never seen that in RC2).

Uncaught exception at scripts/Modify/SplitIntoEqualParts/SplitIntoEqualParts.js:174: Error: :-1:-1: REntity: Argument 0 is not of type REntity *REntity *.
<native>(RLineEntityPointer(0xb73b4c8)) at -1
<anonymous>(op = RAddObjectsOperation(0xb733790), argLine = RLineEntityPointer(0xb73b4c8)) at scripts/Modify/SplitIntoEqualParts/SplitIntoEqualParts.js:174
<anonymous>(op = RAddObjectsOperation(0xb733790)) at scripts/Modify/SplitIntoEqualParts/SplitIntoEqualParts.js:111
<anonymous>(true) at scripts/Modify/SplitIntoEqualParts/SplitIntoEqualParts.js:95
<anonymous>() at /home/martin/workspace/rsframework/scripts/Modify/../EAction.js:1150
<anonymous>() at scripts/Modify/SplitIntoEqualParts/SplitIntoEqualParts.js:73
<global>() at -1
174	        line.copyAttributesFrom(argLine);

qsdb> argLine
RLineEntityPointer(0xb73b4c8)

Split entities: start angle must be entered in degrees * 1rad (converted from degrees to rad twice)

See:
http://www.ribbonsoft.com/rsforum/viewtopic.php?f=32&t=1909

Would it be possible to use the Split command on Ellipse or on Spline curve?

Now it works on lines, arcs and circles only.......

Break up spline at given point, break out segment, etc.

Set up a spline with control points let’s say of the order 3.
Clone it 3 times with some offset in x&y.
Edit the degree property and set 1ste to 1, 2nd to 2, aso
Draw select partially from right to left.
Those of the order 1 and 4 aren’t selected.

Regards

Closed splines (Control points) are saved as “not closed” with a new knot (when DXF is closed and re-opened).
Is this behavious intended ?

Imported splines which typically represent lines, circles or arcs (explicit knot vector given) are sometimes wrongly identified as invalid by the OpenNURBS library.
This results in splines that are loaded and displayed correctly but are not selectable.

Hi guys,

I’m trying to create an spline to a complex library component, but it seems splines are not working properly. I would appreciate some help. These are minimum scripts to demonstrate the problem:

Example 1:

include("scripts/simple.js");

function TesteSpline() {
}

TesteSpline.init = function(formWidget) {
    if (!isNull(formWidget)) {
        TesteSpline.widgets = getWidgets(formWidget);
    }
};

TesteSpline.generate = function(documentInterface, file) {
    return TesteSpline.criarCorpo(documentInterface);
};

TesteSpline.generatePreview = function(documentInterface, iconSize) {
};

TesteSpline.criarCorpo = function(documentInterface) {

    addSpline([[0,0],[20,30],[100,100],[110,120]], false); // it doesn't work :-(
    addLine(0,0, 100,100);  // it works!!!

};

Example 2:

include("scripts/library.js");

function TesteSpline() {
}

TesteSpline.init = function(formWidget) {
    if (!isNull(formWidget)) {
        TesteSpline.widgets = getWidgets(formWidget);
    }
};

TesteSpline.generate = function(documentInterface, file) {
    return TesteSpline.criarCorpo(documentInterface);
};

TesteSpline.generatePreview = function(documentInterface, iconSize) {
};

TesteSpline.criarCorpo = function(documentInterface) {
    var addOperation = new RAddObjectsOperation(false);
    var doc = documentInterface.getDocument()
    // Spline
    var cavaData = new RSplineData();
    cavaData.appendFitPoint(new RVector(0,0));
    cavaData.appendFitPoint(new RVector(10,10));
    cavaData.appendFitPoint(new RVector(30,30));
    cavaData.isClosed = false;
  
    // It doesn't work
    var cava = new RSplineEntity(doc,cavaData);
    addOperation.addObject(cava);

    // it works
    var textData = new RTextData(new RVector(2,10),new RVector(2,10),0.4,0.4,0,0,0,0,1,"Hello","Arial",false,false,0,false);
    addOperation.addObject(new RTextEntity(doc,textData));

    return addOperation;
};