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

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.

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.

add parameter to REntity::clone to allow cloning without cloning object ID.

QMdiChild widgets in an QMdiArea receive repaint and mouse events even if they are not active which slows down the user interface when having multiple MDI children open.

Long term, QMdiArea might have to be replaced with something else.

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?

Disable

Adjust Version

Application

Deployment

Don't forget

Check List

Ports

I only noticed today (perhaps they were available earlier?) that there are 64 bit binaries for windows; I suppose these are true 64 bit.

Yet, the installer prompts me to put them into “Programs (x86)”, where all the 32bit software lives, I guess - this seems to be a pure convention though, the application runs just fine.

Maybe the reason is, that the 32bit version was installed before; Maybe it should change? Maybe it should stay, so that there are not two?

After each update, I add a dot before the ~user/opt folder (and in the program launcher) created by QCAD to unclutter my file manager’s appearance. Would be easy, I think, to make the installer put the program directly in ~user/.opt, and nobody would miss that folder while browsing through daily used files.

And what about installing the program as root, so all users of a computer could use it without personal installs, and only personal setting files created by users would be kept in ~user/.opt/qcam.

Jean-Claude

For all the Linux VI editor geeks, can you disable the <ESC> function in the text edit mode. <ESC> maps to <cancel>. If anything it should map to <ok>. Which creates no harm as it can be later undone. I have accidentally lost edits countless times due to an unbreakable habit.

As it says on the tin - please add script generator for Qt 5.6.2.

The startup script still forces a QT-style; Getting bored of that one, qcad runs fine with the system default style - probably that was a qt4 thing, that can be removed, so it blends better with the DE?

18c18 /opt/qcad/qcad
< LD_LIBRARY_PATH=”$DIR” “$binary” -style plastique “[email protected]” —

LD_LIBRARY_PATH=”$DIR” “$binary” “[email protected]”

... for the Option bar.

Since the launcher batch no longer requests “-style plastique” QT wants to apply the native style of the desktop environment. This fails on a headless system (or where the current user has no graphical shell to connect to) with the message “Gtk-WARNING **: cannot open display: “. Fortunately, QT provides a workaround in addtion to the new “platform=offscreen” flag.

In the tools that set -no-gui, beforehand export these variables into the environment

export QT_STYLE_OVERRIDE=""
export QT_QPA_PLATFORM=offscreen
export DISPLAY=""

PS: QT-offscreen will not find fonts; unfortunately the workaround only allows for a single directory to search them (I need helvetica):

export QT_QPA_FONTDIR="/usr/local/share/fonts/type1"

Maybe that should get reported upstream, so that like LD_LIBRARY_PATH several directories could be specified.

 FS#1604  was issued because of non-intuitive hierarchy of the preferences for the Explode function.
The task comment recieved explains the funcionallity in details not found elsewhere.

Indentation of the phrase ‘Spline Segments:’ suggest hierarchy.
Graying out the drop down box for the number of spline segments establish hierarchy.

Please add script bindings for Qt 5.9.4, thank you.

Without any selection.
Entities on a locked layer can be selected after choosing:

Asumed wrong
- Modify DI
- Modify B2
- Modify D3
- Modify MT

Questionable
- Modify RM
- Modify CH
- Modify RN Less severe
- Modify OF
- Modify OH
- Modify SS

Regards

Please take a look at 1898 again. There is a problem.

Win7pro 32bit Wininstaller Qcadpro 3.23.0

With a polyline.

Select the poly.
Pick any reference point of a vertex.
Place it on any of its neighboring vertex reference points.

A null-segment is created.
The placement can not be undone by re-picking the reference point.
Can be Undone/Redone.
The action can result from editing the vertex coordinates.
When exploding null-entities are created.

This action should delete:
- if the target is next: the picked vertex. (incl. start or end-1)
- if the target is prior: the targetted vertex. (incl. start or end-1)
- if the target is and next and prior: both the prior and the picked vertex.

As the user intentionally places any vertex reference points on:
- any excluding its neighbors:
→ the intented nature is ‘Self-Touching’, ‘Self-Crossing’ or ‘Trace-Back’.
- any of its neighbors:
→ the intention is to delete the segment(s).

Regards

if possible, extend create_makeself script to create a tar.gz in addition to the executable installer, so we have both in the end.

Create and extend part library.

Find Existing Files

Parameterized Items

Links

[mostly old] Generate Items Automatically

<!-- XML document defines a name template to use for the generated parts: -->
"DIN_912_M%1_L%2""din_912.js""DXF"
	<!-- Attributes to use for the name template -->
	"d"
	"L"
 
	<!-- For each type of the specific part, we define some parameters that 
		are identical for that type (here M3): -->
	"3""5.5""2.5""3""18"
		<!-- For each of these elements, a DXF file is generated. This DXF file 
			is generated with file name "DIN_912_M3_L22.dxf" and parameters d="3" D="5.5" 
			s="2.5" k="3" b="18" L="22": -->
		"var1"
		"var2"
		"60"
 
 
	"M4""7""3""4""3""20"
		"var1"
 
 
	"var1"
		"22"
		"25"
		"30"
		"35"
		"40"
		"45"
		"50"
 
 
	"var2"
		"70"
 
 
 

Cheat Sheet which lists all QCAD tools with icon, key code and explanation

Possibly two versions for Windows / Linux and Mac

Implement RImageEntity and related classes.

DONE

POSTPONED

Create block from selection

Implement snap restrictions

Set relative zero point tool.

Lock relative zero tool

Implement layer locking

Implement isometric projection tool

Split up library browser as separate, QCAD independent tool.

TODO

DONE

Motivation

Interface with QCAD 3

QCAD launches library browser for example as:
./QCAD -autostart scripts/Tools/LibraryBrowser/LibraryBrowser.js

Add license header for all ECMAScript files.

Invastiagte QPainter warnings when running QCAD in -no-gui mode

See forum:
http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1653&start=45

Port CXF font editor to QCAD 3.
- Load CXF fonts (load glyphs into blocks)
- Save back to CXF format

Prompted by d9beb4 - this is actually fixed in current upstream sources (by killing bzero in favor of memset, which is the right thing to do).

It might worth considering to update the spatialindex component.

The Linetype Names in the pull-down menu for Layer are hardly readable - it seams to me that the description is used twice (in different ways) in each row.
Till 3.6.4 the Information was short and clear.

I just installed qcad-3.7.0-pro-linux-x86_32 on my up-to-date debian sid system.
When I choose the “Pen” to be visible in the toolbar, the line type is not useable at all, because the drop-down menu is far too narrow.
After deleting QCAD3.conf the drop-down menu appeared wide after the first startup of QCAD. After the second startup it appeared narrow again.
Got the same result on another 32bit installation, a 64bit installation, all debian sid/kde and the windows version 32bit (only tried with wine).

See:
http://www.qcad.org/rsforum/viewtopic.php?f=73&t=4566

Since updating to QCAD 3.16 on MacOS, my dimension font face suddenly changed to something very unattractive and I can’t figure out how to reset it. I tried deleting QCAD and all references to it in ~/Library and then reinstalling, but no luck. Something weird has gone wrong with QCAD’s fonts.

The font change has made it impossible to open and redraw many DXF files because the new font face is larger and wider spaced and it ruins the layout of many documents.

Attached is an example of what the same DXF file looked like in the prior QCAD version, and the new version. No change to the DXF file.

Dan.

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

After I remove the .dll files from the pro trial version, right click stop working on Windows 10.
I went a little further to try identifying which of the 5 files specifically causes right click to stop working, and I found that it is qcadproscripts.dll. The presence or absence of the other 4 dll files that make up the pro version has no influence on this behavior.