QCAD Bugtracker

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.)

Many times, after pressing the space bar to access the command line, accidentally an space character is added at the start of the line. It’s very difficult to see it.

The result is an error like this:

Invalid coordinate or distance ' @20,20'.

The request is for the command line parser to just ignore leading spaces.

Thank you.

Point styles are ignored after setting them in Application Preferences.

See this post: http://www.qcad.org/rsforum/viewtopic.php?f=33&t=3553

Thanks.

I find it a bit annoying that after executing a command by issuing some points in the command line, the command line retains the focus.

This means an extra Escape key press, and sometimes my hotkeys are just sent in plain text to the command line if I forget to escape.

Something like this:

- hotkey: ss (stretch)
- click for first point
- click for second point
- click for reference
- hotkey: eh (restrict horizontal)
- spacebar
- enter distance by hand
- return (execute)

At this point, if I want to repeat another “stretch” command, I have to disable the horizontal restriction by hand (en), and start again.

The problem is that if I forget to press the Escape key, my “en” command is issued in the command line, and I keep looking at the screen because the hotkey was not issued.

What would be desirable IMHO after a command execution would be to reset any restrictions applied and remove focus from command line.

Arrow heads on leaders are missing every time files are opened.

Exploding polylines which are closed both geometrically (first vertex equals last vertex) and logically (closed property is true) results in an additional zero length line after the last segment.

In some cases, loose arc segments result in errors.
See:
http://www.qcad.org/rsforum/viewtopic.php?f=33&t=3573

This problem is USB Flash drive related.

First of all, QCAD does not show the flash drive a drive where data can be stored, but it does when one wants to open a file.

If one then did open a file from the flash drive, saving it back tot he flash drive change the permission of the entire drive to read only and I could not manage to change that other than formatting the drive.

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

Zooming in or out repeatedly (keeping + or - key pressed or using mouse wheel) shows the drawing at incorrect offsets in between frames with the correct offset.

Original report:

Zoom in and out with the Mouse wheel is working but it is unfortunately jumping in a zickzack course.

Saving MText with linefeeds in escaped text causes corruption of file.

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

Offset shown in print preview does not match offset on paper / in PDF file.

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

Edit > Duplicate duplicates all

In the scaling dialogue of the german version (and likely other dialogues too) there appears the term ‘Fukuspunkt’. This should probably rather read ‘Fokuspunkt’ or ‘Fußpunkt’. It points at the reference center for the scaling operation.

The QCAD Community Edition isn’t able to read / import dxf files with a German “Umlaut” like ä,ö, ü in the dxf file name.
If I change the file name from a “ä” into a “ae” QCAD CE will open the file flawless.

Modify > Matrix transformation: crashes for transformation matrices which rotate and uniformly scale the selection.

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

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

Currently, DXF files from QCAD contain the dxflib version number used to write them, but not the QCAD version number. It would be nice to have the full QCAD version number and build information saved in the DXF file, in case it is necessary to reconstruct the environment that was used to generate a particular file.

Documentation for “Angle Bisector (L, B)” The labels for illustrations of number of bisectors are upside down and reversed.

Explode Solids into closed polylines with 3 or 4 vertices.

Remember last used settings in bitmap export dialog (width, height, resolution, margin, background color).

Break out segment / Auto trim again arc is not a sharp cut to the arc (to long or to short),
Break out manual can’t snap to a line/arc intersection,

Add support for PLINEWID: user defined polyline width per segment start / end.

Crop marks and page tags are not in the correct position.

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

Unter dem Werkzeug “Kreiswerkzeuge” “Zentrum, Durchmesser” bekomme ich leider nicht “Zentrum Durchmesser” sondern “Durchmesser Links Unten”.

Version:
QCAD 3.10

Gruß
Stefan

Please double check the functionality of the Print options - I think that there are not correct working.

Move Paper position = OK,
Autofit drawing to paper = out of center, wrong scale
Autofit pages to drawing = to many pages are used,
Auto center = out of center,

Layers with leading or trailing spaces are skipped when importing DXF/DWG files.

Crash due to unhandled exception when using polyline offset on polylines with extreme coordinates.

Scenario 1:
like to use “Breakout segment” on a spline,
Status bar tells me that I CAN use this tool on a spline,
Breakout: works,
Undo: works,
Everything fine ...

Scenario 2:
like to use “Breakout manual” on a spline,
Status bar tells me NOT to use this tool on a spline but ...
Breakout manual: works,
Undo: works,
I think just the status bar needs an Infotext update.

Scenario 3:
like to use “Auto Trim” on a spline,
Status bar tells me NOT to use this tool on a spline but ...
Auto Trim: works,
Undo: works NOT,
I think the status bar needs an Infotext update and I guess in the undo function is a bug.

Right now the “Select Contour” feature behaves like a “Select each and every connected line”.
I think that was not the intended purpose, so I report this as a bug.

I tested it on a honeycomb structure and instead of selecting just the outer contour it selected also every line inside the structure, which were connected to the contour.

Print Preview:
Black and white/Greyscale mode doesn’t works on Text.

I defined new attributes in a 3.11.0 drawing. I can’t get it working.
I loaded an old drawing, knowing that there are working attribute in - there are not anymore working in 3.11.0

Synchronize Attributes doesn’t helps to solve the problem.

Old drawing attached ...

Hi there,
if I put commands in command line to prepare my environment on desktop (GY , GP) - all works fine. These commands will be executed and also repeated in command window.
The command GB should work too, but I receive the error in command window:

"unknown command or invalid coordinate or value 'gb' "

If put all commands while my mouse has focus in my working area, all three commands are working.
I need this functionality to write al little script to setup my well known working environment with QCAD (set up tools, open needed files ...).
What goes wrong?
Greetings from Bavaria ... Lutz

please see below:

http://www.qcad.org/rsforum/viewtopic.php?f=107&t=3781

After saving an open designed Spline QCad will open it the next time as a closed spline.
Trying to fix this in the Property Manager using “Closed Periodic yes/no” leads to an open but broken spline.

Pic 1 = designed
Pic 2 = saved/opened from HD
Pic 3 = Try to fix this with the Property Manager

All such functions in the api seem to be use the spelling Linetype (with lower-case t) while every function call in the test code does use LineType instead.

Report is for version 3.7.5 as it was the only version I found to download on the qcad.org webpage.
Sourceforge also didn’t seem to have any downloads and while I found a few dxflib clones on GitHub, none seemed official or up-to-date.
But maybe I’m just blind

Point entities are not shown in drawing area.

Erroneous block recursion detected when placing, moving large blocks due to update interruption on mouse moves.

Dear Andrew, this might seem an obsolete feature, though I recently tried to look it up, the man-page ;) So attached a quick shot; please use if you like and do not frown the additional maintenance. (quick test: man -l /tmp/qcad.1)

In the application / drawing text-settings, I find some fonts that should not be defined as font at all.
ISO 9985-11 is the THAI codetable (byte). (The once original drawing character drawing-specs in the sixties was ISO 9985)
UNICODE is the new third party 16 bit character codetable, (and has to be UTF8 recoded to fit in a normal computer).
A font does not equals a codetable and there names should not be mixed up.

In top of the font-settings a field ‘Codetable:’ should be added with the choice between ‘ISO9985-1 (Latin1)’ or ‘Unicode’,
where ISO9985-1 (Latin1) refers to the US(Extended)ASCII-set.

Keep in mind some QCAD-edited drawings should and ought to be downward-dxf-compatible with older (ASCII)-versions and software.

Optionally show context menu when right-mouse button is clicked on top of entity.

Originally from FS#1111: “Furthermore, the two named applications show that it’s easily possible to combine dragging (mouse pressed) and context menu (mouse clicked) on the same mouse button.
Providing a context menu would increase the usability especially for people used to Windows default applications.
I.e. deleting, copying, creating polylines from segments, breaking up blocks/polylines would be functions I’d find useful in a context menu.”

In Printpreview. Scaling the print does not scale the drawing smaller, but the paper -size larger. This is unexpected.

One should scale the drawing down to available paper size, not the other way.

Scaling is not done at the natural intuitive analog manner, with surprising results.

When scaling, all visible attributes becomes smaller; lineweigth too

See added pdf.

1. Add user defined hatch pattern to patterns directory
2. Create drawing using that hatch pattern
3. Save drawing
4. Pattern stored with hatch entity does not match user defined pattern

Hi,

In the process of printing a A4-drawing on a A4 page, (Glue-)margin-settings in millimeters is used.
Left 10 mm, Top 5 mm, Right 5 mm, Bottom 5 mm. Printer HP2500C, A4, B&W, Draftmode.

For some odd reasons, at last minute and only accessable via [Properties] the Drawing-settings are overruled by the Application-setting qcad-bin, in a default Letter page settings (and margins?), and the page needs manualy loading.

If qcad-bin page is set to Millimeters, Page A4, the result is not correct; the drawing margins are ignored

Affects drawings with block referenced to empty block for auto zoom and command line tools (dwg2bmp, dwg2pdf, ...).

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);