QCAD Bugtracker

dimension arrows not visible in draft mode

I think Husky may have found a bug, please see topic:

http://www.qcad.org/rsforum/viewtopic.php?f=31&t=3239&p=11643#p11643

@Husky, hope you don’t mind me adding this for you.

- Create new empty drawing
- Make layer 0 invisible or lock it
- Dimension > Leader
- Set start point

Community 3.15.5.3 (Git 9c49f08b), FreeBSD 10.3, Qt 5.5.1

Start the Dimension Leader tool, click a point. While the rubber line is active, click the “Arrow head” option to toggle it (the effect is seen on the rubber line immediately). Now click it again to toggle. The entire dimension disappears with no appreciable trace left anywhere. The DL tool stays active.

Expected outcome would be for the dimension to just toggle the arrow head style.

This only seems to happen if this double-toggling is done as long as no segment is actually created yet (i.e. once at least one segment is actually set, the repeated toggling works as expected).

If boundary lines do not start at the same height, the continuing dimensioning (DC) does not work reliably. This results in incorrect dimensions that often cannot be recognized.

To reproduce:

1. Draw a rectangle.
2. DH, draw a dimension (the base dimension).
3. Move that dimension’s text to a new position.
4. DC, continue that dimension.

The text of the continued dimension will show up on top of that of the base dimension. Expected behaviour would be that it would show up on top of the continued dimension (standard placement).

Please see attached pic.

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

(I originally described the problem in the forum: https://qcad.org/rsforum/viewtopic.php?f=33&t=5721 )
(The problem was also reproduced by user “Husky” so it not installation specific.)

I have a model where one of the details is as shown in attachment 1

However, when I create a viewport and display the part in the the layout the angular measurement is another. See attachment 2.

In the model it should be noted that the part displayed is a detail copied with a different scale as to Zoom in on a detail in order to put dimensions on it. It was created by copying a part of the model and pasting it back in the model but with 3x zoom.

I have also included the full .dxf file in the hope that it helps you both reproduce and fix this issue

Note: The same problem seems to also produce “ghostlines” in other viewports in the layout which is not present in the model. Removing the angular measurement also removed the ghostline. You can observe the issue by looking at layout2 and you can see a line (dimension layer) going from top right corner of the viewport towards the lower left. This line is not present in the model and appears to be some strange extension to the angular dimension the detail that is just to the top right in the model.

System:
Macbook Pro 15”, OS X 10.13.6

(Can also be reproduced in Linux version)

QCad version:

Version: 3.21.2.0 (3.21.2)
Build Date: Jul 9 2018
Revision: f9cea14
Qt Version: 5.10.0
Architecture: x86_64
Compiler: Clang 8.0.0

Dimension - Aligned, not working with context menu.

When dimensioning this particular line in this position I get an Aligned Dimension of 868.6059. Offsetting this line from its original position I get the correct dimension of 19.0320, as shown in my GIF file. All other dimension in the drawing are correct. So what have I not set up or realised. I have moved the drawing to another area of the drawing and still get the same result.
Regards.
Firstime.

Hi,

It seems that QCAD and Autocad treat solid fills differently. Here is attached
example and its view in QCAD and autocadws.com web service. I found that order
of vertices is important.

Thank you
Mikhail

Linux Fedora 21, kde 4.14.7, QCAD version 3.9.4. QCAD Pro add-on and QCAD/CAM add-on disabled.

Clicking on ‘Save As’ or ‘Open’, even when showing an empty drawing, freezes the program. A dialog shows up, but is completely grayed out. QCAD then stops responding completely (so far for about an hour), and has to be killed.

In the process, a warning shows up in the terminal:
Warning: KGlobal::locale(): Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work

(’Open Recent’ and ‘Save’ does seem to work, and can (presently) be used as kind of a workaround, since I’m only working on one file at the moment.)

conducive to host presentations and video clip http://www.askweddingdress.net plus size beach wedding dresses , photography shooting , http://www.askweddingdress.net plus size dresses leaving a lovely second. additional affordable wedding ceremony dresses on 1luckybride 1 reader asks: What exactly are all of the legal actions and the way do you go about receiving your title altered? Is there an inventory of other things which has to alter, http://www.askweddingdress.net bridal gown dresses like your financial institution accounts, http://www.askweddingdress.net short brides dresses charge cards, insurance coverage, and so on http://www.askweddingdress.net brides mothers dresses http://www.askweddingdress.net bridal bridesmaid dresses .? I used to be gonna start into the best way to go about this when I recognized we’ve an intensive post on “How To Alter Your Surname Whenever you Get Married”on our weddings web page http://www.askweddingdress.net muslim wedding dresses . Study it it is useful! 1 factor to become conscious of, specifically in case your honeymoon is not using location appropriate following the marriage ceremony: http://www.askweddingdress.net vintage short dresses Ensure your identify lines up on all of the paperwork necessary to journey. As an example, your driver’s license http://www.askweddingdress.net/evening-dresses.html vintage gowns dress

Hallo Andrew,

I had updated QCAD/CAM to 3.23.0.2 and I am confronted with a major bug in the toolpath generator.

Windows 7-64
3.0.9
Detect duplicates tool not working properly.
Selecting this tool causes program to lag endlessly and malfunctions.
To reproduce bug:
1. Select all entities.
2. Select duplicates tool.
3. Nothing happens.
4. Select duplicate tool again and...bug!

Please see also http://www.qcad.org/rsforum/viewtopic.php?f=32&t=5745

By saving a drawing QCAD is destroying the cross-hatches

• Save drawings on exit
• 10min time limit
• markers in
  • PDF export
  • BMP export
  • SVG export
  • printing

Define grid origin

Default settings (Application preferences) for “Printing colors” shows no effect on a “Grayscale” or a “Black and white” setting.
Regardless the setting a new drawing is always presented with a “Full color” adjustment.

Application Preferences > Defaults for New Drawings > Drawing Units

Do not save new selected value, It keeps “Inch”.

Could be changed per file in Edit > Drawing Preferences. I normally use Millimeter. I have no tested in command line / automation mode.

Error tested in:
Mac OS X 10.11.2 El Capitan
Mac OX X 10.7.5 Server Lion
Windows 10 (also with QCad fresh install)

It would be great if the user could choose a default template for new drawings.

There exists already a “File → New from Template” feature, where I can choose a template, but in most cases I want my new drawings to be based on my default template.
It would be very convenient if there is an option to set the default template and use it for the “File → New” function.

It was nice to specify the default Format for saving files. 2010 is too young for distribution to unknown users, better use 2004 or so...

Default paper might be configured as 210×297 inches if inch is chosen as default unit.

I couldn’t find where to specify the default “Line weight” for a newly created layer. Default proposed is 0,25 mm ISO and I would like to continue to uses 0,00 mm. Because, these lines are very thick when i look at my drawing in

The R2010 DXF and R2010 DWG formats produced by QCAD 3 RC5 cannot be opened by Visio 2010.

Error message:
Cannot open file. The file may not be a DWG or DXF file, it may not be in a supported version of the DWG file format, or it may be corrupted. Check the file and try again.

Prerequisites:

1. QCAD 3 RC5
2. Visio 2010 with all updates installed

Steps to reproduce:

1. Open QCAD 3 RC5 and create a basic drawing. Save using the default file types (R2010 DXF or DWG)
2. Open Visio and create a new drawing.
3. Go to Insert tab and click CAD Drawing. select drawing created above.
4. Observe error message

Additional info:

• When I use Save As in QCAD 3 RC5 and select any previous file format, Visio can insert the drawing. The problem I’m seeing with this part is that on a more complex drawing, the spacing/alignment is messed up (items aren’t in their proper spacing).

Other observations with a more complex file:

• If I open a R2010 versioned file in Solidworks and then save it back out as a dxf file again, Visio will properly insert the drawing with correct spacing/alignment

• If I open the file in QCAD 2.2.2.0 and then save as Drawing Exchange (*.DXF) it inserts properly in Visio with correct spacing/alignment.

• If I open the file in QCAD 2.2.2.0 and then save as Drawing Exchange R12 (*.DXF) it inserts in Visio but the alignment is off (similar to problem above).

File attached for reference.

Thanks,
Rich

First. I am not able to find OS selection for macOS Sierra so I choose Mac OS X.
I noticed that when I opened my drawing, I saw dimensions on drawing showed ‘156?6’ instead of ‘156.6’ in prior version I had installed. Probably in 3.16.5

So I opened Dimension Settings page to review and found when opening Dimension Settings under Drawing Preferences,
Dimension Settings does not show. It remains blank.

Then I clicked on other settings menu item from left and clicked back on the Dimension Settings I was able to see the Dimension setting.
However; when I closed the dialog and try to open the Dimension Settings again, I am not able to see the settings page at all. Just blank. I can see other settings page fine.

One time when I was able to see the Dimension Setting, I noticed that the Separator symbol was blank. So I updated that to ‘.’ and hit OK.
The drawing still shows ‘156?6’ instead of expected ‘156.6’.

It seems the separator symbol is not being saved for some reason.

Starting qcad Beta 3 with command line argument -always-load-scripts will bring up debugger:

Uncaught exception at /opt/qcad-3.0.0-beta3-prof-linux/scripts/library.js:2: RangeError: Maximum call stack size exceeded.
2 include(”sprintf.js”);

When attempting to use the Lengthen tool, the Qt Script Debugger was activated. The following exception was noted:

Welcome to the Qt Script debugger.
Debugger commands start with a . (period).
Any other input will be evaluated by the script interpreter.
Type “.help” for help.

Uncaught exception at scripts/Modify/Lengthen/Lengthen.js:137: TypeError: Result of expression ‘this.entity.trimStartPoint’ [undefined] is not a function.
137 this.entity.trimStartPoint(is);

The application then crashed and report was sent to Apple.

6a5c66 on both FreeBSD and Linux (particular example on FreeBSD). The following diff is present, but it should be a no-op in this regard:

--- a/shared.pri
+++ b/shared.pri
@@ -11,6 +11,7 @@ DEFINES += QCAD_DLL
 # output directory:
 CONFIG(debug, debug|release) {
     ROUTDIR = debug
+    QMAKE_CXXFLAGS_DEBUG += -ggdb3
 } else {
     ROUTDIR = release
 }

qmake-qt4 qcad.pro CONFIG=debug

Goes on a while, then bombs off at

g++ -c -pipe -g -ggdb3 -Wall -W -fPIC -DQCAD_DLL -DPTHREADS -DHAVE_PTHREAD_H
    -I/usr/local/share/qt4/mkspecs/freebsd-g++
    -I.
    -I/usr/local/include/qt4/QtHelp
    -I/usr/local/include/qt4/QtDesigner
    -I/usr/local/include/qt4/QtUiTools
    -I../../../../core
    -I../../../../core/math
    -I../../../../grid
    -I../../../../snap
    -I../../../../gui
    -I../../../../entity
    -I../../../../operations
    -I../../../../scripting
    -I../../../../stemmer
    -I../../../../scripting/ecmaapi
    -I../../../../scripting/ecmaapi/generated
    -I../../../../scripting/ecmaapi/adapters
    -I../../../../io/dxf
    -I../../../../spatialindex
    -I../../../../3rdparty
    -I.
    -I/usr/local/include/qt4
    -I/usr/local/include
    -o debug/qtscript_Global.o
    ../../generated_cpp/com_trolltech_qt_core/qtscript_Global.cpp

../../generated_cpp/com_trolltech_qt_core/qtscript_Global.cpp:6:25: error: qmetaobject.h: No such file or directory
../../generated_cpp/com_trolltech_qt_core/qtscript_Global.cpp:8:20: error: QVariant: No such file or directory
../../generated_cpp/com_trolltech_qt_core/qtscript_Global.cpp:10:21: error: qglobal.h: No such file or directory

The corresponding good release compile line is:

g++ -c -pipe -O2 -Wall -W -pthread -D_THREAD_SAFE -fPIC -DQCAD_DLL
    -DPTHREADS -DHAVE_PTHREAD_H -DQT_NO_DEBUG -DQT_WEBKIT_LIB
    -DQT_SCRIPT_LIB -DQT_SCRIPTTOOLS_LIB -DQT_SVG_LIB -DQT_SQL_LIB
    -DQT_XMLPATTERNS_LIB -DQT_XML_LIB -DQT_OPENGL_LIB -DQT_GUI_LIB
    -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
    -I/usr/local/share/qt4/mkspecs/freebsd-g++
    -I.
    -I/usr/local/include/qt4/QtHelp
    -I/usr/local/include/qt4/QtDesigner
    -I/usr/local/include/qt4/QtUiTools
    -I/usr/local/include/qt4/QtCore
    -I/usr/local/include/qt4/QtNetwork
    -I/usr/local/include/qt4/QtGui
    -I/usr/local/include/qt4/QtOpenGL
    -I/usr/local/include/qt4/QtXml
    -I/usr/local/include/qt4/QtXmlPatterns
    -I/usr/local/include/qt4/QtSql
    -I/usr/local/include/qt4/QtSvg
    -I/usr/local/include/qt4/QtScriptTools
    -I/usr/local/include/qt4/QtScript
    -I/usr/local/include/qt4/QtWebKit
    -I/usr/local/include/qt4
    -I../../../../core
    -I../../../../core/math
    -I../../../../grid
    -I../../../../snap
    -I../../../../gui
    -I../../../../entity
    -I../../../../operations
    -I../../../../scripting
    -I../../../../stemmer
    -I../../../../scripting/ecmaapi
    -I../../../../scripting/ecmaapi/generated
    -I../../../../scripting/ecmaapi/adapters
    -I../../../../io/dxf
    -I../../../../spatialindex
    -I../../../../3rdparty
    -I.
    -I/usr/local/include
    -Irelease
    -I/usr/local/include/qt4
    -I/usr/local/include
    -o release/qtscript_Global.o
    ../../generated_cpp/com_trolltech_qt_core/qtscript_Global.cpp

The diff between them is suspiciously big (unique items only):

includes-wise:

--- incbad      2013-10-20 11:45:37.302711863 +0200
+++ incgood     2013-10-20 11:45:31.899711566 +0200
@@ -16,7 +16,19 @@
 -I../../../../stemmer
 -I/usr/local/include
 -I/usr/local/include/qt4
+-I/usr/local/include/qt4/QtCore
 -I/usr/local/include/qt4/QtDesigner
+-I/usr/local/include/qt4/QtGui
 -I/usr/local/include/qt4/QtHelp
+-I/usr/local/include/qt4/QtNetwork
+-I/usr/local/include/qt4/QtOpenGL
+-I/usr/local/include/qt4/QtScript
+-I/usr/local/include/qt4/QtScriptTools
+-I/usr/local/include/qt4/QtSql
+-I/usr/local/include/qt4/QtSvg
 -I/usr/local/include/qt4/QtUiTools
+-I/usr/local/include/qt4/QtWebKit
+-I/usr/local/include/qt4/QtXml
+-I/usr/local/include/qt4/QtXmlPatterns
 -I/usr/local/share/qt4/mkspecs/freebsd-g++
+-Irelease

Defines-wise:

--- defbad      2013-10-20 11:51:22.405716122 +0200
+++ defgood     2013-10-20 11:52:05.362693170 +0200
@@ -1,3 +1,17 @@
 -DHAVE_PTHREAD_H
 -DPTHREADS
 -DQCAD_DLL
+-DQT_CORE_LIB
+-DQT_GUI_LIB
+-DQT_NETWORK_LIB
+-DQT_NO_DEBUG
+-DQT_OPENGL_LIB
+-DQT_SCRIPTTOOLS_LIB
+-DQT_SCRIPT_LIB
+-DQT_SHARED
+-DQT_SQL_LIB
+-DQT_SVG_LIB
+-DQT_WEBKIT_LIB
+-DQT_XMLPATTERNS_LIB
+-DQT_XML_LIB
+-D_THREAD_SAFE

qmetaobject.h is on Qt/ and QtCore/, both of which is missing from the debug include path.

On Linux, it’s complaining about QtScript/QScriptExtensionPlugin (which is in /usr/include/qt4), diffs between includes:

--- incbad      2013-10-20 12:04:32.612710645 +0200
+++ incgood     2013-10-20 12:04:58.129714235 +0200
@@ -14,7 +14,21 @@
 -I../../../../snap
 -I../../../../spatialindex
 -I../../../../stemmer
+-I/usr/X11R6/include
+-I/usr/include/qt4
+-I/usr/include/qt4/QtCore
 -I/usr/include/qt4/QtDesigner
+-I/usr/include/qt4/QtGui
 -I/usr/include/qt4/QtHelp
+-I/usr/include/qt4/QtNetwork
+-I/usr/include/qt4/QtOpenGL
+-I/usr/include/qt4/QtScript
+-I/usr/include/qt4/QtScriptTools
+-I/usr/include/qt4/QtSql
+-I/usr/include/qt4/QtSvg
 -I/usr/include/qt4/QtUiTools
+-I/usr/include/qt4/QtWebKit
+-I/usr/include/qt4/QtXml
+-I/usr/include/qt4/QtXmlPatterns
 -I/usr/share/qt4/mkspecs/linux-g++-64
+-Irelease

Defines:

--- defbad      2013-10-20 12:07:16.961712166 +0200
+++ defgood     2013-10-20 12:07:38.831670098 +0200
@@ -1,4 +1,18 @@
 -DHAVE_PTHREAD_H
 -DPTHREADS
 -DQCAD_DLL
+-DQT_CORE_LIB
+-DQT_GUI_LIB
+-DQT_NETWORK_LIB
+-DQT_NO_DEBUG
+-DQT_OPENGL_LIB
+-DQT_SCRIPTTOOLS_LIB
+-DQT_SCRIPT_LIB
+-DQT_SHARED
+-DQT_SQL_LIB
+-DQT_SVG_LIB
 -DQT_WEBKIT
+-DQT_WEBKIT_LIB
+-DQT_XMLPATTERNS_LIB
+-DQT_XML_LIB
+-D_REENTRANT

I am considering pushing the following diff:

--- a/src/core/RSPlatform.cpp
+++ b/src/core/RSPlatform.cpp
@@ -205,25 +205,6 @@ int RS::getCpuCores() {
     cores = sysinfo.dwNumberOfProcessors;
 #elif defined(Q_OS_UNIX)
     cores = sysconf( _SC_NPROCESSORS_ONLN );
-#elif defined (Q_OS_MAC) || defined (Q_OS_BSD4) || [...]
-    nt mib[4];
-    size_t len;
-
-    /* set the mib for hw.ncpu */
-    mib[0] = CTL_HW;
-    mib[1] = HW_AVAILCPU; // alternatively, try HW_NCPU;
-
-    /* get the number of CPUs from the system */
-    sysctl(mib, 2, &cores, &len, NULL, 0);
-
-    if (cores < 1) {
-        mib[1] = HW_NCPU;
-        sysctl( mib, 2, &cores, &len, NULL, 0 );
-    }
-#elif defined(Q_OS_HPUX)
-    cores = mpctl(MPC_GETNUMSPUS, NULL, NULL);
-#elif defined(Q_OS_IRIX)
-    cores = sysconf( _SC_NPROC_ONLN );
 #endif

(truncated list to manage size)

I see that most of this was put in there as a kind of a note-to-self originally, however _SC_NPROCESSORS_ONLN is implemented by every realistically possible targets anyway, so for all practical purposes, this is dead weight.

A couple of questions remain, though:

• #ifdef Q_OS_WIN32 should probably be Q_OS_WIN, so as to include win64 as well.
• Assuming the real purpose for this function is to determine how many parts a particular task is to be split into in the future, if and when QCAD gets the need to split expensive tasks among multiple CPUS, “core” probably shouldn’t be static - CPUs are hot-pluggable today, and while one probably doesn’t do that on a laptop, it’s not unfeasible in, say, a VDI environment.

Thoughts?

no task description

QCAD2 offered the user to specify in the program settings where these directories should be/go, and took the first one in each list as default; QCAD3 only offers to enter auxiliary library and template directories and has no provisions for defaults.

All associated data (scipts, templates, libraries, patterns, fonts) is stored under the program directory, exactly where it should not be. Windows 7 and higher default prevent modifying the programs directory by redirecting the writes.
An extra user-input during the Windows install process would be in order.

QCAD3 should offer the user to specify any and all data directories involved (including the auto save), and make it possible to specify a default for each.
This list could be initialised with the installation defaults, or default to the installation directories when empty.

data points display as either a dot (.) or a plus sign (+) on output to pdf or printer. There appears to be no constancy or control over the behaviour. Any way it could be forced to behave like Qcad-2 (i.e. line-weight controlled dot (.) ???

When we create a draft in version 2.2.2 we put dashed lines and the length is 0. We see a dash lines. (see attach file).

When we open the same draft in the version 3.3.2 we don’t see the dashed lines we see a continous lines.

If I changed in the dxf this lines DASHED 370 0 per DASHED 370 5 and changes the preference of the drawing it’s work.

But we don’t want to open all of 180000 drawings to change the length of the dashed lines from 0 to 5. We want that the version 3 print the dashed lines as the version 2.

Thanks

Eric

Chat from  FS#194  singled out, so that can be closed.

Dash patterns in BETA2 are very much out of proportion. BETA2 always PG exports 1:1 and only scales strokes so that in the final rendering they match what a technical drawing would show. As dash patterns depend on stroke, both current stroke and final scale have to be brought in accord.

The patch below also restores the alignment of dashes, so that dashed lines do not end in a gap, at least in most occasions.

--- SvgExporterPG-orig.js	2011-09-15 23:11:40.000000000 +0200
+++ SvgExporterPG.js	2011-10-07 13:28:04.085376719 +0200
@@ -384,32 +384,29 @@
         continuous = true;
     }
     if (!continuous) {
-        //p.scale(this.getPatternFactor());
-        p.scale(1/this.scale);
+        // dash and gap lengths are to be proportional to line weight
+        // beware: line weight unit is 100 times millimeters, convert to current unit
+        // beware: the viewer scales lengths differently from weight
+        p.scale(RUnit.convert(this.weight / 100.0, RS.Millimeter, this.svgUnit) / this.scale);
         var num = p.getNumDashes();
-        var str = "";
+        var str = [];
         for ( var i = 0; i < num; ++i) {
             var len = Math.abs(p.getDashLengthAt(i));
-            // see FS#192:
-            //len = this.convert(len);
-            str += "" + len;
-            if (i < num - 1) {
-                str += ",";
-            }
-        }
-        additionalStyles += "stroke-dasharray:" + str;
-        
-        // does more harm than good
-//        if (isShape(this.shape)) {
-//            var length = this.shape.getLength();
-//            if (isNaN(this.offset)) {
-//                this.offset = this.getPatternOffset(length, p);
-//            } else {
-//                var num = Math.ceil(this.offset / p.getPatternLength());
-        //                this.offset -= num * p.getPatternLength();
-        //            }
-        //            additionalStyles += ";stroke-dashoffset:" + this.offset;
-        //        }
+            str.push(len);
+        }
+        additionalStyles += "stroke-dasharray:" + str.join(",");
+
+        // center dash-array
+        if (isShape(this.shape) && isFinite(this.shape.getLength())) {
+            var length = this.shape.getLength();
+            if (isNaN(this.offset)) {
+                this.offset = -this.getPatternOffset(length, p);
+            } else {
+                var num = Math.ceil(this.offset / p.getPatternLength());
+                this.offset -= num * p.getPatternLength();
+            }
+            additionalStyles += ";stroke-dashoffset:" + this.offset;
+        }
     }