Hallo Andrew

If CAM layer invisible do not 3D Simulate and do not write G-code.

I use gcode ripper for some of my jobs. (see here: https://www.scorchworks.com/Gcoderipper/gcoderipper.html) This is a large python script that I use to wrap flat code around a cylinder for engraving. What I would like to see is a way to run it from my own custom post processor that I wrote for my machine. Maybe some kind of keyword that allows me to specify an arbitrary external command with some parameters. It would be very helpful to me. I create a lot of ad-hock jobs to run.

Thanks,
Chuck Tilbury

• add test for all kind of dimensions

add “update required file” to the context menu shown in the result window

1. copy the actual file to the directory “required”
2. run the test again
3. test result should be “passed” now

example file generator: adjust the print settings automatically, so the example file can be immediately printed to the chosen paper format / orientation without having to adjust the scale / offset

Open

Homepage

Wikipedia

Flyspray

Done

Homepage

The QCAD scripts, that contain a great deal of functionality in the QCAD framework, are so to say open source, in the limited, still powerful, sense that they can be read, inspected and single-handedly adapted to local needs. Wouldn’t it make sense to store these in a public source code repository?

So to allow closer tracking of development, eg. Of course, all of the scripts would then have to know which release of the /kernel/ they require as a support. But that should be a good thing anyways, as soon as a community of framework users arises, wasn’t it?

Library - Architecture is showing only four (4) symbols:
“ffl, north, uparrow and winv”.
Is this correct?

Thanks in advance

Regards

Reinhard(RM)

Loading any larger dxf file takes very long because of this line:
istr.imbue(std::locale(”C”));

The call to std::locale is very slow. File-loading can be speed up by approximately factor 5 times on my system when replacing it. I just removed that line and instead added the following in DL_Dxf::in so it is changed only once per file:

std::locale oldLocale = std::locale::global(std::locale(”C”)); // use dot in numbers
while (readDxfGroups(fp, creationInterface)) {}
std::locale::global(oldLocale);

Move cursor near spline, e.g. when drawing line with auto snap active.

• initial start (no library browser DB present)
• Linux vostro 2.6.37.6-0.5-desktop #1 SMP PREEMPT 2011-04-25 21:48:33 +0200 i686 i686 i386 GNU/Linux
• DWG / DXF files: 79
• SVG files: 684
• RDF files: 729

real    1m37.298s
user    1m35.101s
sys     0m0.806s

Preview when inserting image slow

Cannot move/dock command line to right hand pane!

Regards

clive

Slower selection / manipulation compared to QCAD 2.

Snap defaults to auto. Auto snap gets slow in areas where there are many places it can snap to.

Opening a 4 MB dwg file results in no-response for about five minutes. Opening the same file with DraftSight takes less than five seconds.

In the “Application Preferences”-menu a click on submenu “Shortcuts and Commands” freeze the application for a view minutes.

Complex blocks: moving with drag and drop shows whole block as preview (slow)

Inverting the current selection is significantly slower than select all, deselect all or other selection tools.

Selecting a great number of entities (>10000) can be slow, likely due to updating the property editor.

Preview performance can be improved by projecting only once and then moving / pasting the projection.

Windows 7 Professional 64bit SP1

File > Open shows empty dialog for 1 minute, then shows dialog contents.

Hatches in blocks cause poor performance while (auto-)snapping.
The lines that make up those hatches are included in the search for intersection points which is not desirable.

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

Splines with hundreds of control points or fit points can cause hangs when using auto snap near them.

Merely clicking on ‘Draw Order’, and usualy unintended, halts the system for several seconds up to several tens of seconds.

Intel(R) Core(TM) i7-2600K CPU @ 3.40Ghz
4,00 GB RAM installed 3,49 GB usable
32-bit Operating System
Windows 7 Professional SP1

Hi!

when working with files containing many not connected elements (non-poly-line elements) a double click can cause a coffee-break easily. The search for connected entities easily takes over 5 minutes on an up to date machine ([email protected]) with files that are pretty standard in size (2 or 3 MB file size ascii dxf). Adding an interruption-method would be suitable (for example by pressing escape).

attached a file with a polyline of 13000 entities and a second file with just everything duplicated. When exploding the polyline and double clicking an element it takes quite a while until all elements are selected. (this is not an extreme example, I had sometimes 10 minutes of waiting with slightly bigger files, accidently double clicking something).

also an improved algorithm for the search would help to speed up the selection. (e.g. divide the area in smaller parts, do the search there, or an option to search only in the visible view port of the document)

Martin

Texts justified and/or formatted in dxf or dwg files generated by Autocad not presented correctly when the file is opened by QCad, follow file for verification.

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

When switching from one drawing to another, the 3D view is updated which can be slow, especially for drawings with many text entities.

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

Hallo Andrew,

Fiddling with the drill-toolpath error, a solution seems to be to add the drill location as a ‘single point’ in the ‘source’ sublayer. I am using this as a Bug Work Around.

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.