|
2552 | QCAD (main) | Bug Report | Low | Windows shortcut Alt + Underlined Key fails partly in m... | Assigned | |
|
Task Description
Reason: Same underlined keys are used for different menus
Select and Snap = S, Dimension and Info = I, Modify and Misc = M,
|
|
2068 | QCAD Community Edition | Bug Report | Very Low | Non-english text in upper/lower index becomes UTF code | Assigned | |
|
Task Description
How to reproduce.
1. Create a text field with some non-english words in the upper index. (see attached pic1.png) 2. Save the project and close QCAD. 3. Run QCAD and open same project. 4. Now upper/lower indexed text becomes not human readable UTF codes. (see attached pic2.png)
Tried different fonts - doesn’t help.
Linux ntb-kirill 3.10.0-1062.12.1.el7.x86_64 #1 SMP Tue Feb 4 23:02:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.7.1908 (Core)
|
|
2315 | QCAD Community Edition | Bug Report | Low | Crash after ~10-th times move Spline nodes | Assigned | |
|
Task Description
1. Create spline 2. Move spline nodes. After ~10 times move qcad is crashed with backtrace: Thread 9 “Thread (pooled)” received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff56dc9640 (LWP 8224)] 0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848) at /usr/include/qt5/QtCore/qlist.h:492 492 current→v = new T(*reinterpret_cast<T*>(src→v)); (gdb) bt #0 0x00007ffff66fabf2 in QList<QSharedPointer<RShape> >::node_copy (this=<optimized out>, src=0x55537c59e758, to=0x555557f66408, from=0x55537cfdc848)
at /usr/include/qt5/QtCore/qlist.h:492
#1 QList<QSharedPointer<RShape> >::detach_helper (alloc=<optimized out>, this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:835 #2 QList<QSharedPointer<RShape> >::detach_helper (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:849 #3 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178 #4 QList<QSharedPointer<RShape> >::detach (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:178 #5 0x00007ffff686182a in QList<QSharedPointer<RShape> >::end (this=<optimized out>, this=<optimized out>) at /usr/include/qt5/QtCore/qlist.h:342 #6 QList<QSharedPointer<RShape> >::last (this=0×555557311620) at /usr/include/qt5/QtCore/qlist.h:364 #7 RSpline::appendToExploded (this=0×555557311510, line=...) at math/RSpline.cpp:964 #8 0x00007ffff6867059 in RSpline::getExploded (this=0×555557311510, segments=1457293328) at math/RSpline.cpp:919 #9 0x00007ffff686682a in RSpline::getLength (this=this@entry=0×555557311510) at math/RSpline.cpp:1026 #10 0x00007ffff6c11490 in RSplineData::getLength (this=<optimized out>, this=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineData.h:178 #11 RSplineEntity::getProperty (this=0x5555573114a0, propertyTypeId=..., humanReadable=<optimized out>, noAttributes=<optimized out>,
showOnRequest=<optimized out>) at /usr/src/debug/qcad-3.27.0.0/src/entity/RSplineEntity.cpp:253
#12 0x00007ffff67cc214 in RPropertyEditor::computePropertyValue (ccProp=...) at /usr/src/debug/qcad-3.27.0.0/src/core/RPropertyEditor.cpp:574 #13 0x00007ffff67d298f in QtConcurrent::FunctionWrapper1<void, RProperty&>::operator() (u=..., this=0x555557757f18)
at /usr/include/qt5/QtConcurrent/qtconcurrentfunctionwrappers.h:80
#14 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIteration (it=..., this=0x555557757ee0)
at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:68
#15 QtConcurrent::MapKernel<QList<RProperty>::iterator, QtConcurrent::FunctionWrapper1<void, RProperty&> >::runIterations (this=0x555557757ee0,
sequenceBeginIterator=..., beginIndex=<optimized out>, endIndex=15) at /usr/include/qt5/QtConcurrent/qtconcurrentmapkernel.h:77
#16 0x00007ffff67d2c9d in QtConcurrent::IterateKernel<QList<RProperty>::iterator, void>::forThreadFunction (this=0x555557757ee0)
at /usr/include/qt5/QtConcurrent/qtconcurrentiteratekernel.h:255
#17 0x00007ffff44b5b2d in QtConcurrent::ThreadEngineBase::run (this=0x555557757f20) at qtconcurrentthreadengine.cpp:302 #18 0x00007ffff59c8d52 in QThreadPoolThread::run (this=0x555556198b10) at thread/qthreadpool.cpp:100 #19 0x00007ffff59c5a61 in QThreadPrivate::start (arg=0x555556198b10) at thread/qthread_unix.cpp:329 #20 0x00007ffff546c717 in start_thread (arg=<optimized out>) at pthread_create.c:435 #21 0x00007ffff54f018c in clone3 () from /lib64/libc.so.6 (
|
|
2386 | QCAD Community Edition | Bug Report | Low | Label "Linear format" missing in Property Editor | Assigned | |
|
Task Description
no task description |
|
2391 | QCAD Community Edition | Bug Report | Low | Fix Dark Theme for Linux | Assigned | |
|
Task Description
The dark theme for Linux is broken:
- Some icons have dark background (expected) and black foreground color (that should be replaced by white of very light gray) - Some icons have light background (not cohesive with the theme). - The command history shows dark blue font on dark gray background. - The grid’s ruler shows black font over dark background for the numbers. - The icons folder is missing in the GitHub repository, but other themes have that folder. - The general icons (open, save, and so on) are not dark theme friendly. A better approach for maybe all the themes would be to use something like the breeze icons pack for LibreOffice, and it will have the added benefit of making the app look more modern.
The icons issue is the biggest problem. They should probably replace the black color for white or very light gray. Even the red accent color is not ideal for dark themes, is not the main issue.
Attached is an image that show the problems and another that shows LibreOffice with the Dark Breeze theme for reference.
|
|
2405 | QCAD Community Edition | Bug Report | Low | Dimension scaling not working | Assigned | |
|
Task Description
I’m using QCAD Community Edition 3.27.7 on Windows 11.
When I started my drawing, I was able to change the size scale factor of (existing) dimensions using “Edit/Drawing Preferences/Dimension/Dimension Settings/Size scale factor”. However, suddenly this feature stopped working and now I cannot switch the dimension scale factor any longer.
I used this feature to be able to adapt the scale factor of the dimensions when printing in different scales. I.e. all my drawings are in “original” size but when it comes to printing, I print some parts in scale 1:2 (in which case I used to set the size scale factor of the dimensions to 2) and some parts in scale 1:10 (in which case I used to set the scale factor of the dimensions to 10). Using this procedure, the dimensions have the same size (font size, arrow size, gaps etc.) on both drawings.
I have attached the drawing, that shows the described issues.
|
|
1843 | QCAD/CAM | Bug Report | Low | Creating ToolPath Stalls | Assigned | |
|
Task Description
Hi Andrew,
Still working with and on CAM HPGL for the HP7580 pen plotter.
I have added a penplotter test drawing, that might be used for testing en callibrating plotter and pens. You may add it to the Examples-directory.
QCAD has a lot of trouble creating toolpaths and exports. Much too often it shuts itself down, or gets stalled. Why? I am not sure.
|
|
1847 | QCAD/CAM | Bug Report | Low | BUG MEMORY | Assigned | |
|
Task Description
Hi Andrew,
Still working on creating HPGL.PLT toolpaths for the HP7580 pen plotter. QCAD has some trouble creating toolpaths. Too often it shuts itself down, or the PC gets stalled.
Recreating the same error however is possible
|
|
1913 | QCAD/CAM | Bug Report | Low | 3D Simulation Behaves odd | Assigned | |
|
Task Description
Hallo Andrew,
testing the drill toolpath I used single point markers.
In 3D simulation the tool drills the toolpath AND uses the drill as a mill.
Cam Export and generated G-code is not effected.
|
|
1971 | QCAD/CAM | Bug Report | Low | CAD/CAM 3D Simulator | Assigned | |
|
Task Description
Hallo Andrew,
Found a bug in the 3D Simulator execution
|
|
2167 | QCAD/CAM | Bug Report | Low | Comma format decimal separator fails ZSafety CAM config... | Assigned | |
1 |
Task Description
QCAD/CAM Trial package Win installer 32 bit Version: 3.25.2.0 (3.25.2) Internet: QCAD.org Build Date: Sep 4 2020 Revision: 4a61501 Qt Version: 5.13.2 Architecture: i386 Compiler: Unknown
Local decimal separator is ‘,’ (comma) In CAM configuration .. Z Levels .. Safety level
Using nn,nnn the output is Nxx G0 Znn Using nn.nnn the output is Nxx G0 Znn.nnn
Drop down boxes are all in dot format. Didn’t try anything else yet
Regards, CVH
|
|
513 | Translation | Bug Report | Low | Translation errors | Assigned | |
|
Task Description
If you spot an error in the translated user interface of QCAD, please add a comment to this task or submit your translation at http://translate.qcad.org. Thank you for your help!
Wenn Sie einen Fehler in der übersetzten Benutzeroberfläche von QCAD erkennen, fügen Sie bitte einen Kommentar zu diesem Report hinzu oder geben Sie Ihre Übersetzung ein unter http://translate.qcad.org. Vielen Dank für Ihre Hilfe!
Si vous remarquez une erreur dans l’interface utilisateur traduite de QCAD, veuillez ajouter un commentaire à cette tâche ou soumettre votre traduction à http://translate.qcad.org. Merci pour votre aide!
Si detecta un error en la interfaz de usuario traducida de QCAD, añada un comentario a esta tarea o envíe su traducción a http://translate.qcad.org. Gracias por tu ayuda!
Se si rileva un errore nell’interfaccia utente tradotta di QCAD, si prega di aggiungere un commento a questo compito o di inviare la traduzione a http://translate.qcad.org. Obrigado por sua ajuda!
Se você detectar um erro na interface de usuário traduzida do QCAD, adicione um comentário a esta tarefa ou envie sua tradução para http://translate.qcad.org. Obrigado pela sua ajuda!
Als u een fout ziet in de vertaalde gebruikersinterface van QCAD, voeg dan een opmerking toe aan deze taak of stuur uw vertaling naar http://translate.qcad.org. Bedankt voor uw hulp!
|
|
1887 | dwg2bmp | Feature Request | Low | Add "-max-lineweight" option for dwg2bmp | Assigned | |
2 |
Task Description
Hi there,
A friendly request to add the option to set a maximum lineweight for raster conversions via dwg2bmp.
Depending on the LW configuration of the CAD file, rasterization operations sometimes yield terrible results (see attachment). This would also mirror the similar “-min-lineweight” options available on “dwg2svg” and “dwg2pdf” (although not on “dwg2bmp”).
See also: https://qcad.org/rsforum/viewtopic.php?f=32&t=6298
Thanks!
|
|
1888 | dwg2bmp | Feature Request | Low | Add support to disable hatch rendering on "dwg2bmp" | Assigned | |
1 |
Task Description
Hi!
A friendly request to add an option to disable hatch rendering on “dwg2bmp” conversions.
Depending on the nature of the conversion and the density of the hatch, this may render unintelligible images (see attachments). The option could look like “-t, -nohatch” to indicate hatches should be hidden before rendering. This could potentially become an option too for “dwg2svg” or “dwg2pdf.”
Amazing product, thank you so much!
|
|
1922 | dwg2bmp | Feature Request | Very Low | Add error message when requesting raster for a non-exis... | Assigned | |
|
Task Description
It would be nice if QCAD spit some kind of warning message when trying to render a layer with a name that doesn’t exist (and perhaps render nothing), rather than silently rendering an empty image. :D
See https://qcad.org/rsforum/viewtopic.php?f=33&t=6453
|
|
1700 | dwg2pdf | Feature Request | Low | dwg2pdf: output multiple layouts | Assigned | |
|
Task Description
Add support to specify multiple blocks (layouts) to output (one per page).
|
|
1823 | dwg2pdf | Feature Request | Low | plotting error to pdf a Dwg where the view port is not ... | Assigned | |
|
Task Description
When trying to plot a dwg or a dxf to pdf where the viewport is orientated to a different angle than north up the data in the view port is plotted north up. see attached DWG and pdf for clarification.
|
|
1824 | dwg2pdf | Feature Request | Low | dwg2pdf does not obey frozen layers in paper-space view... | Assigned | |
|
Task Description
We currently have a paper-space using two viewports with different layers from the model-space frozen. Unfortunately in the pdf output the layers which are frozen show up. dwg2pdf should obey the specific frozen layer for each viewport
|
|
1542 | dwg2svg | Feature Request | Low | dwg2svg: add switch to show only given layer(s) | Assigned | |
|
Task Description
Implement a command line switch to only show a list of given layers for dwg2* command line tools.
|
|
2378 | dwg2svg | Feature Request | Low | Export attributes on block references as namespaced XML... | Assigned | |
|
Task Description
dwg2svg supports exporting the layer name (and probably others?) as namespaced XML attributes (`qs:layer`) which works well. However I’d like to export block attributes as well, as seen on the following screenshot:
https://imgur.com/a/wUd0adE
(...so `ROOM_NAME` would become `qs:ROOM_NAME=”Eötvös terem”` on the respective XML element).
Thanks in advance.
|
|
1506 | dxflib | Feature Request | Low | writeVPort parameters | Assigned | |
|
Task Description
Add parameters to the function DL_Dxf::writeVPort. This way users will be able to specify the desired viewport.
Is the github the official repository? Are pull requests sent there accepted?
|
|
1863 | ECMAScript | Feature Request | Low | WidgetFactory.saveState: save state of checkable QGroup... | Assigned | |
|
Task Description
QGroupBox widgets with <property name=”checkable”> are not saved in Qcad3.conf
|
|
173 | QCAD (main) | Feature Request | Low | explode text to letters | Assigned | |
1 |
Task Description
implement
|
|
208 | QCAD (main) | Feature Request | Low | SVG export: support custom line weights | Assigned | |
|
Task Description
Find way to support custom line weights for SVG export. See also forum thread: http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1594
|
|
228 | QCAD (main) | Feature Request | Low | Insert current date (and other fields) | Assigned | |
9 |
Task Description
Insert field into drawing that displays current date, file name, ...
|
|
275 | QCAD (main) | Feature Request | Low | Rounding all corners of a polyline | Assigned | |
3 |
Task Description
Modify - Round - Click polyline - round all corners
|
|
277 | QCAD (main) | Feature Request | Low | command line arguments: allow class name after -exec | Assigned | |
|
Task Description
command line arguments: allow class name after -exec
|
|
293 | QCAD (main) | Feature Request | Low | multi-select for blocks | Assigned | |
|
Task Description
It would be nice if one could select multiple blocks in the block list at once (holding ctrl or ctrl+shift). Main purpose would be to delete them if they are not needed anymore. If possible, the same applies to layers.
|
|
316 | QCAD (main) | Feature Request | Low | Blocks list and selected block | Assigned | |
|
Task Description
Wouldn’t it be nice, if selecting a block in model view would somehow highlight (just like clicking a block in the list does) the selected block in the “Block List” window?
(Feature request sounds a little harsh, enhancement proposal would seem more apt.)
|
|
355 | QCAD (main) | Feature Request | Low | Remember function for dimension Option | Assigned | |
|
Task Description
I think it would be nice to have more flexibility for Prefix etc. option (not only the drop down with a given choice) and a remember function for all those fields like postfix and tolerance.
Why Remember Function: If I use a postfix like <>” in the postfix field I’m only able to use it for this particular dimension type at this time. If I change the type (from Horizontal to vertical or what ever) I have always to repeat my postfix. The same with tolerances.
|
|
396 | QCAD (main) | Feature Request | Low | Blocks: moving blocks: show bounding box | Assigned | |
|
Task Description
Blocks: moving complex blocks with drag and drop should show bounding box as preview
|
|
455 | QCAD (main) | Feature Request | Low | logical operations for polylines | Assigned | |
2 |
Task Description
A missing feature in my work are logical operations (combine, intersect, ..) for polylines
Example: Draw some elements, select them, say combine. The result will be the outline of all elements.
|
|
467 | QCAD (main) | Feature Request | Low | Feature request for new Arc tool option to add to Arc s... | Assigned | |
2 |
Task Description
For and behalf of mandrena
To add another Arc tool option in Arc tools set:
1.Specify Start point for Arc. 2.Specify End point for Arc. 3.Specify “Tangent” direction (without being restricted in input field) so you can visually select a point on your desired Tangent line!
|
|
500 | QCAD (main) | Feature Request | Low | Autohide Side Panel | Assigned | |
1 |
Task Description
it would be ideal to be able to have the option to autohide the side panel to increase the visible drawing space when working on a small screen.
|
|
502 | QCAD (main) | Feature Request | Low | Points on line: enter distance instead of number of poi... | Assigned | |
2 |
Task Description
Points on line: enter distance instead of number of points as a variant of the tool or as a new tool.
|
|
503 | QCAD (main) | Feature Request | Low | Convert entities to points with a fixed distance | Assigned | |
|
Task Description
Select lines, arcs, ... and convert them to points along the lines, arcs, ... with a fixed distance.
See also forum at: http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1834
|
|
512 | QCAD (main) | Feature Request | Low | Modify stretch and Restrict ortho | Assigned | |
1 |
Task Description
The modify stretch tool wants first and second corner, start and end point, then starts afresh. When I turn on restrict horizontally eg to align two points between start and end, the restriction sticks and I have to call restrict none, to be able to perform the next iteration, set the first corner then.
So, in the quest for a comfortable user interface, it was nice, if the modify stretch first/second corners parameter setting was not affected by current restrict/ortho etc. settings. Actually, that does not make any sense at all anyways, does it, a rectangle is defined by two degrees of freedom, isnt it?
|
|
514 | QCAD (main) | Feature Request | Low | Punktpestimmung Intersection manual muss immer wieder n... | Assigned | |
|
Task Description
Beispiel: Zeichnen einer Linie (Line two points) mit Punktbestimmung. Wähle ich für die Punktbestimmung z.B. “End” bleibe ich in diesem Modus bis ich etwas anderes wähle. Gut
Wähle ich für die Punktbestimmung “Intersection manual” muss ich dies für jeden Punkt immer wieder neu anwählen. Schlecht
|
|
516 | QCAD (main) | Feature Request | Low | To add option to 'print only' selected area. | Assigned | |
2 |
Task Description
To add the option to ‘print only’ selected area in a drawing.
|
|
519 | QCAD (main) | Feature Request | Low | Press tab to access first control in options tool bar | Assigned | |
1 |
Task Description
See: http://www.ribbonsoft.com/rsforum/viewtopic.php?t=1867
Apparently this was possible in QCAD 2 due to the default behavior of Qt.
|
|
525 | QCAD (main) | Feature Request | Low | change the printed symbol of points | Assigned | |
1 |
Task Description
Hi,
in QCAD3 RC2 points were printed as crosses, in QCAD3 RC4 they are printed as (very little) points. I think this isn’t a bug but a feature.
It would be nice if one could change this behaviour / select the symbol of points.
Best regards - Stefan
This is a double post of http://www.ribbonsoft.com/rsforum/viewtopic.php?p=5870#5870 as suggested there.
|
|
554 | QCAD (main) | Feature Request | Low | Auswahlbox sollte auch mit der Shift Taste Bereiche dem... | Assigned | |
|
Task Description
Ziehe ich mit der Maus eine normale Auswahlbox kann ich Elemente markieren. Möchte ich einzelne Bereiche wieder herausnehmen muss ich alle Elemente einzeln anklicken (mit gedrückter Shift Taste). Ich kann zwar dies komfortabler gestalten mit der Select → (De -) Select Contour Funktion welche aber erst über das Menue aufgerufen werden muss.
So wie ich einzelne Elemente mit der Maus auswählen und mit der Shift-Maus Funktion deselektieren kann wäre es schön wenn die Shift Taste auch bei Auswahlbereichen direkt zum deselektieren eingesetzt werden könnte.
|
|
564 | QCAD (main) | Feature Request | Low | Settings organisation in level | Assigned | |
|
Task Description
As an old professional “documentation writer and user inteface designer” but IMHO, I’m not convinced that the “Application preferences” are correctly organised for ease of understanding and using them. These settings are organised in 2 levels. Some of the first levels have their own settings (e.g. “Graphics view”) while most others don’t (e.g. “Load/save”). May I humbly suggest some consistency rules : - no sub-level if there is only one subject - no items on main level if there are already 1 or more sub-level(s). For instance : - sub-level “Default Dimension settings” under “Dimension” is the only sub-level : then move these items under main level “Dimension” and suppress the sub-level ; - the items under “Graphics view” main level (with several sub-levels)could be in a sub-level named “General” ; Actually, “Graphics view” main level is the only one which has both its own items and sub-levels )) ?
|
|
566 | QCAD (main) | Feature Request | Low | Shortkey for rectangle text rotation | Assigned | |
1 |
Task Description
I would like to get a shortkey like ‘+’ to rotate text at 90° clockwise.
|
|
579 | QCAD (main) | Feature Request | Low | Copy layers / blocks | Assigned | |
2 |
Task Description
Duplicate (copy, clone) a layer with or without entities on it. New name can be specified by user.
|
|
586 | QCAD (main) | Feature Request | Low | File open dialog with preview | Assigned | |
1 |
Task Description
Since this is not supported by Qt anymore, this would likely have to be implemented from scratch.
|
|
588 | QCAD (main) | Feature Request | Low | Bemaßung Prefix Dropdown mit eigenen Vorgaben erweitern... | Assigned | |
|
Task Description
Es wäre Arbeitserleichternd wenn ich bei den Optionen für Bemaßungen (Prefix/Postfix) eigene Präferenzen speichern könnte so das diese in allen Zeichnungen von mir verfügbar wären. Zudem wäre es wünschenswert dieses nicht nur bei den Prefix sondern auch bei den Postfix Angaben nutzen zu können was dann alle(?) Manipulationen erschlagen würde.
Siehe auch: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=11&t=1966
|
|
596 | QCAD (main) | Feature Request | Low | Tool "Lengthen" mit "Total" erweitern oder .... | Assigned | |
1 |
Task Description
Eine oft Hilfreiche Zeit/Klick sparende Erweiterung wäre eine “Total” Option bei dem “Lengthen” Tool.
Aktuell ist es mit dieser Funktion möglich ein Element zu verlängern oder zu verkürzen um den Amount X. Der Referenzpunkt (von welchem Ende) kann bestimmt werden.
Die Erweiterung die ich mir wünschen würde wäre auch ein “Total” um ein Element auf eine bestimmte Länge zu bringen ohne einen Taschenrechner benutzen zu müssen. Referenz (welches Ende oder Mitte) sollte (muss) dafür wählbar sein.
Die Funktion “Property editor” stellt bereits über die Geometry Eigenschaften die Möglichkeit zur Verfügung einen “Total” Wert zu manipulieren. Leider bin ich aber hierbei nicht in der Lage zu bestimmen welcher Element Referenzpunkt dafür benutzt werden soll. Könnte ich die Referenz wählen (welches Ende oder Mitte) wäre auch dies dann durchaus akzeptabel
|
|
598 | QCAD (main) | Feature Request | Low | Support tangents between ellipses | Assigned | |
2 |
Task Description
To add support for drawing tangents between ellipses.
See topic: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=31&t=2003
|
|
601 | QCAD (main) | Feature Request | Low | Für Berechnungen neu zu erstellende Elemente Werte von ... | Assigned | |
|
Task Description
Es wäre schön wenn ich Werte wie zum Beispiel Längen von Linien direkt abgreifen könnte um diese weiter in Berechnungen verwenden zu können.
Beispiel: Ich habe eine Linie konstruiert wobei sich eine Länge y ergeben hat.
Nun möchte ich eine Linie zeichnen die 5 mal y sein soll.
Linientool → Wert 5* eingeben und y durch Auswahl mit der Maus von dem vorhandenen Elements übernehmen.
Natürlich könnte ich die Geometrie Info benutzen um den Wert abzulesen oder auch über die Zwischenablage zu benutzen. Ein abgreifen mit der Maus wäre aber schneller, direkter und wahrscheinlich auch mit weniger Fehlern (Human error) verbunden. Wahrscheinlich auch genauer da QCad, denke ich, mit mehr Nachkommastellen rechnet, oder?
|