|
2328 | QCAD (main) | Bug Report | Very Low | drop down, using keyboard | Assigned | |
|
Task Description
Minor issue! When using keyboard to initiate the dropdown menus. I noticed the ALT “D” does not cycle through the headings Draw & Dimension in the same way. ALT “M” cycles though Modify & Misc or ALT “S” cycles though Select & Snap. User Name: StanTibbs E-mail: [email protected]
|
|
2331 | QCAD/CAM | Feature Request | Low | Tabs: Control over on which particular profile used. | Assigned | |
|
Task Description
Currently if I position one Tab (KT) to stacked profiles QCADCAM will use it on ALL in Z matching profiles. Practically in most cases would be to use tabs only on the lowest profile.
It would be nice to have some kind of control on which profile a tab has to be used.
|
|
2336 | QCAD (main) | Feature Request | Low | Add command to go back to previous nested block | Assigned | |
|
Task Description
“em” just always goes back to the main drawing. But for nested blocks, when jumping from edit mode of one block to the next nested block, it would be helpful to have some “ep” to go back to the previous block.
This was discussed at the forums...
|
|
2337 | QCAD (main) | Feature Request | Low | Distance information should be available in 2D and 3D | Assigned | |
|
Task Description
As per https://qcad.org/rsforum/viewtopic.php?f=32&t=9089, I suggest to extend the distance information tools:
* show Delta Z (at least when any of the elements has Z information) * allow switching between 2D and 3D distance * maybe allow to show both * maybe change the text to distinguish between them (”Distance” → “Distance 2D/3D”)
|
|
2339 | QCAD (main) | Feature Request | Low | Block List multible selection | Assigned | |
|
Task Description
It would be nice to have the possibility to select multiple blocks with Shift and/or CTRL + mouse like the Layer List to use a delete etc command on all selected blocks at once.
|
|
2340 | QCAD (main) | Feature Request | Low | Layer List / Block List: Link minus icon to keyboard de... | Assigned | |
|
Task Description
Referring to Layer List / Block List: It would improve the workflow if the Delete key on the keyboard would be linked to the minus icon (Delete). The command ER is also ignored in both list.
|
|
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.
|
|
2381 | QCAD (main) | Bug Report | Low | Crash when modifying toolbar settings | Assigned | |
|
Task Description
QCAD Professional 3.27.6.0 running on macOS 12.4 (21F79)
QCAD sometimes crashes when I am adding or removing items from toolbars. It isn’t consistent and I haven’t seen a pattern about which items trigger the crash. It has happened while editing different files, but I’ve attached attached a very simple example and two crash reports
|
|
2386 | QCAD Community Edition | Bug Report | Low | Label "Linear format" missing in Property Editor | Assigned | |
|
Task Description
no task description |
|
2387 | QCAD (main) | Feature Request | Low | Open Drawings on Layout Block by Default | Assigned | |
|
Task Description
As the layout block contains the drawing sheet, the number, the viewports, it’s the presentable part of the drawing.
Maybe QCAD could be able to save on the dxf the “last state” of the drawing. If I saved on the Model and closed, it would open on Model... and if my last save was on the Layout”n”, it would open on Layout “n”.
At least on my work area, when opening a finished drawing, it’s the ideal for it to be opened in a Layout (if it was the active block while saving).
|
|
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.
|
|
2396 | QCAD (main) | Bug Report | Low | Missing Dim/Label Format information from an extern wri... | Assigned | |
|
Task Description
Please refer to forum topic: https://www.qcad.org/rsforum/viewtopic.php?f=89&t=9556
The attached example file is written with a third party CAD program in R15. Opened in QCAD CE all Dim/Label information are available. If I load this drawing in QCAD Pro the Dim/Label information are lost.
If I load and save the example drawing with CE the newly written dxf is readable in Pro without any issue.
|
|
2398 | QCAD (main) | Feature Request | Low | Excessive Autosave | Assigned | |
|
Task Description
Autosave currently updates the backup file indefinitely regardless of whether the drawing has been modified since the last autosave. Request only update autosave following additional edits since last autosave.
|
|
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.
|
|
2433 | QCAD (main) | Suggestion | Low | Lock Snap [SQ] fails at snap Middle Manual [SN] | Assigned | |
|
Task Description
e.g: If I use content out of the clipboard to insert it multiple times into the drawing with using the Middle Manual snap [SN] the snap can’t be locked [SQ] and I have to reactivated the snap again and again for every following insert. Other snaps like END or CENTER work flawless in this scenario.
|
|
2450 | QCAD (main) | Bug Report | Low | Flip Block with Attributes horizontaly fails | Assigned | |
|
Task Description
A block with Attributes can’t be flipped (Option bar) horizontally. The Attributes will be rotated 180° instead of been mirrored. Other entities in the block flip correctly. Same block flipped vertically works as expected (Mirrored Attributes). Same block flipped with FH or MI works as expected. (Mirrored Attributes).
|
|
2457 | QCAD (main) | Bug Report | Low | Polyline start / end widths not saved for first segment | Assigned | |
|
Task Description
Draw a polyline with a single segment
Set the start and end width of the first vertice / segment (index 0)
Save
Reload
|
|
2461 | dxflib | Bug Report | Very Low | ASCII Control characters not handled correctly in Commu... | Assigned | |
|
Task Description
I see the following problem: When I open a particular DXF file in the Professional Trial version 3.27.9.0 on macOS, “^I” in text fields is expanded to whitespace. When I open the same DXF file in the Community Edition 3.27.9.0 on NetBSD/x86_64 (installed from pkgsrc), “^I” in text fields is visible as “^I”.
|
|
2467 | QCAD (main) | Bug Report | Low | macOS M1/M2 setup with multiple screens: crash during i... | Assigned | |
|
Task Description
I sometimes start QCAD Pro on a project and then go do something else after a while, leaving it open in the background.
At least 5 times now it died in this state, in the background, without user activity, giving me the ‘quit unexpectedly’ dialog.
Here’s some part of the log that macOS collects when that happens:
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------
Process: QCAD-Pro [62952]
Path: /Applications/QCAD-Pro.app/Contents/MacOS/QCAD-Pro
Identifier: org.qcad
Version: 3.28 (3.28.0)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2023-04-15 15:39:31.3443 +0200
OS Version: macOS 13.3.1 (22E261)
Report Version: 12
Anonymous UUID: 7BF39A64-2E31-A624-4A66-896554C6DEC0
Sleep/Wake UUID: 8D811F79-BAFA-4D25-BDA4-DF99AEE2DE0E
Time Awake Since Boot: 300000 seconds
Time Since Wake: 1 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Codes: 0x0000000000000001, 0x0000000000000018
Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [62952]
VM Region Info: 0x18 is not in any region. Bytes before following region: 105553518919656
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
MALLOC_NANO (reserved) 600018000000-600020000000 [128.0M] rw-/rwx SM=NUL ...(unallocated)
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 QtGui 0x104c3b884 QMacCGContext::QMacCGContext(QPainter*) + 44
1 libqmacstyle.dylib 0x1063fe838 0x1063f4000 + 43064
2 libqmacstyle.dylib 0x106405fec 0x1063f4000 + 73708
3 QtWidgets 0x1055263e4 QCommonStyle::drawControl(QStyle::ControlElement, QStyleOption const*, QPainter*, QWidget const*) const + 2132
4 libqmacstyle.dylib 0x10640379c 0x1063f4000 + 63388
5 QtWidgets 0x105562000 0x1054b4000 + 712704
6 QtWidgets 0x10568c474 QTabBar::paintEvent(QPaintEvent*) + 1584
7 QtWidgets 0x105508f70 QWidget::event(QEvent*) + 132
8 QtWidgets 0x10568bcd4 QTabBar::event(QEvent*) + 736
9 QtWidgets 0x1054bf520 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
10 QtWidgets 0x1054c0ffc QApplication::notify(QObject*, QEvent*) + 3396
11 QtCore 0x1065b7570 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 292
12 QtWidgets 0x1054fc214 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 3312
13 QtWidgets 0x105503890 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 864
14 QtWidgets 0x105503780 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 592
15 QtWidgets 0x105503780 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 592
16 QtWidgets 0x105503780 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 592
17 QtWidgets 0x105503780 QWidgetPrivate::paintSiblingsRecursive(QPaintDevice*, QList<QObject*> const&, int, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 592
18 QtWidgets 0x1054fc314 QWidgetPrivate::drawWidget(QPaintDevice*, QRegion const&, QPoint const&, QFlags<QWidgetPrivate::DrawWidgetFlag>, QPainter*, QWidgetRepaintManager*) + 3568
19 QtWidgets 0x105519aec QWidgetRepaintManager::paintAndFlush() + 3872
20 QtWidgets 0x105519d70 QWidgetRepaintManager::sync() + 252
21 QtWidgets 0x105509410 QWidget::event(QEvent*) + 1316
22 QtWidgets 0x105624f10 QMainWindow::event(QEvent*) + 248
23 QtWidgets 0x1054bf520 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272
24 QtWidgets 0x1054c0ffc QApplication::notify(QObject*, QEvent*) + 3396
25 QtCore 0x1065b7570 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 292
26 QtWidgets 0x105516800 QWidgetRepaintManager::sendUpdateRequest(QWidget*, QWidgetRepaintManager::UpdateTime) + 604
27 QtWidgets 0x105516540 void QWidgetRepaintManager::markDirty<QRect>(QRect const&, QWidget*, QWidgetRepaintManager::UpdateTime, QWidgetRepaintManager::BufferState) + 1748
28 QtWidgets 0x10551fdcc 0x1054b4000 + 441804
29 QtCore 0x106600ce4 0x106550000 + 724196
30 QtGui 0x1049b47c4 QWindowPrivate::emitScreenChangedRecursion(QScreen*) + 80
31 QtGui 0x1049aa348 QScreen::~QScreen() + 700
32 QtGui 0x1049aa3b0 QScreen::~QScreen() + 12
33 QtGui 0x1049bec7c QWindowSystemInterface::handleScreenRemoved(QPlatformScreen*) + 36
34 libqcocoa.dylib 0x103de7d80 0x103db8000 + 195968
35 libqcocoa.dylib 0x103de65d0 0x103db8000 + 189904
36 libqcocoa.dylib 0x103dfb014 0x103db8000 + 274452
37 QtCore 0x1065c63d8 QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const + 1072
38 libqcocoa.dylib 0x103dfe45c 0x103db8000 + 287836
39 CoreFoundation 0x18e193240 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 128
40 CoreFoundation 0x18e22ef30 ___CFXRegistrationPost_block_invoke + 88
41 CoreFoundation 0x18e22ee78 _CFXRegistrationPost + 440
42 CoreFoundation 0x18e164580 _CFXNotificationPost + 704
43 Foundation 0x18f0c19e4 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88
44 AppKit 0x1915834bc __67-[NSWindow _updateSettingsSendingScreenChangeNotificationToScreen:]_block_invoke + 496
45 AppKit 0x1913ff7e0 NSPerformVisuallyAtomicChange + 108
46 AppKit 0x1915832c0 -[NSWindow _updateSettingsSendingScreenChangeNotificationToScreen:] + 96
47 AppKit 0x1916c3ec0 -[NSWindow _screenChanged:] + 136
48 AppKit 0x1916c3e18 -[NSWindow _displayChangedSoAdjustWindows:] + 112
49 AppKit 0x191d3156c -[_NSFullScreenContentController displayChanged] + 28
50 AppKit 0x191dd5834 -[_NSFullScreenSpace displayChanged] + 48
51 AppKit 0x191dd4504 _fullScreenInstanceMovedSpaces + 208
52 SkyLight 0x192da9e34 (anonymous namespace)::notify_datagram_handler(unsigned int, CGSDatagramType, void*, unsigned long, void*) + 888
53 SkyLight 0x1930e9c84 CGSDatagramReadStream::dispatchMainQueueDatagrams() + 228
54 SkyLight 0x1930e9b80 invocation function for block in CGSDatagramReadStream::mainQueueWakeup() + 28
55 libdispatch.dylib 0x18df0e874 _dispatch_call_block_and_release + 32
56 libdispatch.dylib 0x18df10400 _dispatch_client_callout + 20
57 libdispatch.dylib 0x18df1ebf8 _dispatch_main_queue_drain + 928
58 libdispatch.dylib 0x18df1e848 _dispatch_main_queue_callback_4CF + 44
59 CoreFoundation 0x18e1dfc88 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 16
60 CoreFoundation 0x18e19d4a8 __CFRunLoopRun + 1992
61 CoreFoundation 0x18e19c58c CFRunLoopRunSpecific + 612
62 HIToolbox 0x1979d1df4 RunCurrentEventLoopInMode + 292
63 HIToolbox 0x1979d1c30 ReceiveNextEventCommon + 648
64 HIToolbox 0x1979d1988 _BlockUntilNextEventMatchingListInModeWithFilter + 76
65 AppKit 0x1913bbf58 _DPSNextEvent + 636
66 AppKit 0x1913bb0f4 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 716
67 AppKit 0x1913af558 -[NSApplication run] + 464
68 libqcocoa.dylib 0x103dcd0d8 0x103db8000 + 86232
69 QtCore 0x1065c0994 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 532
70 QtCore 0x1065b7c0c QCoreApplication::exec() + 128
71 libqcadjsapi.dylib 0x116ab5648 QCoreApplication_WrapperSingleton::exec() + 24
72 libqcadjsapi.dylib 0x11625d1b8 QCoreApplication_WrapperSingleton::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) + 684
73 libqcadjsapi.dylib 0x11625d930 QCoreApplication_WrapperSingleton::qt_metacall(QMetaObject::Call, int, void**) + 100
74 QtQml 0x1045e58f8 0x1044b8000 + 1235192
75 QtQml 0x1045e245c 0x1044b8000 + 1221724
76 QtQml 0x1045e0f30 QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const + 956
77 QtQml 0x1045fef88 QV4::Runtime::CallProperty::call(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value*, int) + 420
78 QtQml 0x10462bc00 0x1044b8000 + 1522688
79 QtQml 0x10462aaec 0x1044b8000 + 1518316
80 QtQml 0x1045a5c18 0x1044b8000 + 973848
81 QtQml 0x1045fef88 QV4::Runtime::CallProperty::call(QV4::ExecutionEngine*, QV4::Value const&, int, QV4::Value*, int) + 420
82 QtQml 0x10462bc00 0x1044b8000 + 1522688
83 QtQml 0x10462aaec 0x1044b8000 + 1518316
84 QtQml 0x1045a5c18 0x1044b8000 + 973848
85 QtQml 0x1045fed60 QV4::Runtime::CallName::call(QV4::ExecutionEngine*, int, QV4::Value*, int) + 388
86 QtQml 0x10462c11c 0x1044b8000 + 1523996
87 QtQml 0x10462aaec 0x1044b8000 + 1518316
88 QtQml 0x1045a2744 QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext*) + 368
89 QtQml 0x104603dfc QV4::Script::run(QV4::Value const*) + 228
90 QtQml 0x10454a5a0 QJSEngine::evaluate(QString const&, QString const&, int, QList<QString>*) + 336
91 libqcadjsapi.dylib 0x11692bf9c RScriptHandlerJs::doScript(QString const&, QList<QString> const&) + 336
92 libqcadcore.dylib 0x1036fd5b8 RScriptHandler::autostart(QString const&, QList<QString> const&) + 2000
93 QCAD-Pro 0x102f7d87c main + 4996
94 dyld 0x18dd67f28 start + 2236
Thread 1:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x18e08aff0 __select + 8
1 CoreFoundation 0x18e1c81e8 __CFSocketManager + 636
2 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
3 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 2:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x18e07ff14 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x18e092240 mach_msg2_internal + 80
2 libsystem_kernel.dylib 0x18e088b78 mach_msg_overwrite + 604
3 libsystem_kernel.dylib 0x18e080290 mach_msg + 24
4 CoreFoundation 0x18e19e8b8 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x18e19d198 __CFRunLoopRun + 1208
6 CoreFoundation 0x18e19c58c CFRunLoopRunSpecific + 612
7 AppKit 0x1914e6508 _NSEventThread + 172
8 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
9 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 3:
0 libsystem_pthread.dylib 0x18e0bad8c start_wqthread + 0
Thread 4:
0 libsystem_pthread.dylib 0x18e0bad8c start_wqthread + 0
Thread 5:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 6:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 7:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 8:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 9:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 10:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 11:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 12:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 13:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 14:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 15:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 16:: Thread (pooled)
0 libsystem_kernel.dylib 0x18e083710 __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x18e0c0574 _pthread_cond_wait + 1232
2 QtCore 0x1067282f4 0x106550000 + 1934068
3 QtCore 0x106727fac 0x106550000 + 1933228
4 QtCore 0x106727ed8 QWaitCondition::wait(QMutex*, QDeadlineTimer) + 108
5 QtCore 0x106722630 0x106550000 + 1910320
6 QtCore 0x10671e374 0x106550000 + 1893236
7 libsystem_pthread.dylib 0x18e0bffa8 _pthread_start + 148
8 libsystem_pthread.dylib 0x18e0bada0 thread_start + 8
Thread 0 crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x000000016ce88f28 x2: 0x000000016ce88f00 x3: 0x000000016ce88f28
x4: 0x000000016ce88d68 x5: 0x0000000000000011 x6: 0x0000000000000000 x7: 0x000000016ce87ed8
x8: 0x0000000113f799f0 x9: 0x0000000106418530 x10: 0x0000000000179f41 x11: 0x0000000000219e00
x12: 0x000000012de03fa8 x13: 0x0000000000000020 x14: 0x000000012de00000 x15: 0x0000000000000020
x16: 0x0000000104c3bb34 x17: 0x000000012dea34d0 x18: 0x0000000000000000 x19: 0x000000016ce88bd8
x20: 0x0000000000000000 x21: 0x000000016ce88f28 x22: 0x000000014de58530 x23: 0x000000014de58530
x24: 0x0000000000000001 x25: 0x0000000000008001 x26: 0x0000000000008000 x27: 0x00000001e9523460
x28: 0x0000000000000002 fp: 0x000000016ce88ba0 lr: 0x0000000104c3b880
sp: 0x000000016ce88b40 pc: 0x0000000104c3b884 cpsr: 0x60001000
far: 0x0000000000000018 esr: 0x92000006 (Data Abort) byte read Translation fault
Binary Images:
0x102f70000 - 0x102f7ffff org.qcad (3.28) <50923e35-b0f4-33ad-87b5-c80b6e07fb18> /Applications/QCAD-Pro.app/Contents/MacOS/QCAD-Pro
0x1035cc000 - 0x1039fffff libqcadcore.dylib (*) <68b6cf9d-e03f-30ac-a74f-0fae66240b13> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadcore.dylib
0x103100000 - 0x1031a3fff libqcadentity.dylib (*) <185c94cd-8860-3723-9c74-185a1b18c0e0> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadentity.dylib
0x10323c000 - 0x103293fff libqcadgui.dylib (*) <57e28a4d-f6fd-3b3d-9465-702d9b0dbb86> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadgui.dylib
0x102ff4000 - 0x103003fff libqcadgrid.dylib (*) <2d7b7164-4c14-3ce7-bbe0-49ec38a68fa0> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadgrid.dylib
0x103050000 - 0x10306ffff libqcadoperations.dylib (*) <c884af96-582c-3be3-a77e-100c27bfbb77> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadoperations.dylib
0x10308c000 - 0x10309ffff libqcadsnap.dylib (*) <0630cbf2-cbeb-3a02-8fa7-e0c17fdb666c> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadsnap.dylib
0x103014000 - 0x10301ffff libqcadspatialindex.dylib (*) <d834db84-bb6b-369c-b967-1148a481ed6f> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadspatialindex.dylib
0x103370000 - 0x1033b7fff libspatialindexnavel.dylib (*) <05a48089-e554-3429-b0c3-eccd0fc9f1f3> /Applications/QCAD-Pro.app/Contents/Frameworks/libspatialindexnavel.dylib
0x103514000 - 0x103573fff org.qt-project.QtOpenGL (6.4) <6fe5bbb7-45dc-316b-8c8f-4d455fee11ad> /Applications/QCAD-Pro.app/Contents/Frameworks/QtOpenGL.framework/Versions/A/QtOpenGL
0x1030b4000 - 0x1030dffff org.qt-project.QtSql (6.4) <3974ce4c-632e-3d00-bbd1-088875642482> /Applications/QCAD-Pro.app/Contents/Frameworks/QtSql.framework/Versions/A/QtSql
0x1032fc000 - 0x103333fff org.qt-project.QtSvg (6.4) <4c4477bd-616f-3de0-912d-934a2b143af2> /Applications/QCAD-Pro.app/Contents/Frameworks/QtSvg.framework/Versions/A/QtSvg
0x103444000 - 0x10345bfff org.qt-project.QtXml (6.4) <e1e4e15c-d26c-3800-b8f1-c8a792ffec55> /Applications/QCAD-Pro.app/Contents/Frameworks/QtXml.framework/Versions/A/QtXml
0x1044b8000 - 0x10482ffff org.qt-project.QtQml (6.4) <51bb2e01-4ec1-3719-a2f6-36cf30380e0e> /Applications/QCAD-Pro.app/Contents/Frameworks/QtQml.framework/Versions/A/QtQml
0x103ea0000 - 0x103fa7fff org.qt-project.QtNetwork (6.4) <2d4bab25-001a-3333-b3db-b95d9aca025f> /Applications/QCAD-Pro.app/Contents/Frameworks/QtNetwork.framework/Versions/A/QtNetwork
0x103474000 - 0x1034bbfff org.qt-project.QtPrintSupport (6.4) <2c160c73-f509-3e7b-b281-1e17179314d2> /Applications/QCAD-Pro.app/Contents/Frameworks/QtPrintSupport.framework/Versions/A/QtPrintSupport
0x1054b4000 - 0x105903fff org.qt-project.QtWidgets (6.4) <d4530615-1625-3bd4-ad4f-c808d616fd39> /Applications/QCAD-Pro.app/Contents/Frameworks/QtWidgets.framework/Versions/A/QtWidgets
0x1048f0000 - 0x104f03fff org.qt-project.QtGui (6.4) <755184d6-c551-391a-b2ed-6413cb06df19> /Applications/QCAD-Pro.app/Contents/Frameworks/QtGui.framework/Versions/A/QtGui
0x106550000 - 0x1069bbfff org.qt-project.QtCore (6.4) <0039ed8f-97d9-3555-a1fb-c8281b2a9e1c> /Applications/QCAD-Pro.app/Contents/Frameworks/QtCore.framework/Versions/A/QtCore
0x102fd4000 - 0x102fd7fff org.qt-project.QtConcurrent (6.4) <b2015105-c358-332c-8b3f-5debfd79c737> /Applications/QCAD-Pro.app/Contents/Frameworks/QtConcurrent.framework/Versions/A/QtConcurrent
0x103d18000 - 0x103d93fff org.qt-project.QtDBus (6.4) <63c9ff9a-567f-3dac-8abc-3c30823ab0c2> /Applications/QCAD-Pro.app/Contents/Frameworks/QtDBus.framework/Versions/A/QtDBus
0x103db8000 - 0x103e4ffff libqcocoa.dylib (*) <d3d12a1e-d996-3265-885a-a8e474f79f50> /Applications/QCAD-Pro.app/Contents/PlugIns/platforms/libqcocoa.dylib
0x1063f4000 - 0x106417fff libqmacstyle.dylib (*) <52b5adc6-8fd3-3577-9c61-ed57cfe4032e> /Applications/QCAD-Pro.app/Contents/PlugIns/styles/libqmacstyle.dylib
0x10dc48000 - 0x110467fff libqcaddwg.dylib (*) <97457f76-7e3d-3eaf-a495-534031592cb6> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcaddwg.dylib
0x106434000 - 0x1064e7fff org.qt-project.QtCore5Compat (6.4) <8437f179-2c2b-3e52-938f-3a0d3dda4d14> /Applications/QCAD-Pro.app/Contents/Frameworks/QtCore5Compat.framework/Versions/A/QtCore5Compat
0x109c34000 - 0x109c87fff libqcaddxf.dylib (*) <6b64540e-e48a-3cdb-96f3-d596dcd2c3e6> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcaddxf.dylib
0x116200000 - 0x11919bfff libqcadjsapi.dylib (*) <3b3a8e88-1c63-3489-8045-f2ddaa719727> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcadjsapi.dylib
0x105464000 - 0x105477fff libqcadstemmer.dylib (*) <7a8fbfa6-eb3a-341b-a3ba-5703dbbdc01d> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadstemmer.dylib
0x109d18000 - 0x109d4ffff libqcadpolygon.dylib (*) <9f63281b-3e5c-3eaa-97a5-206e21f5d899> /Applications/QCAD-Pro.app/Contents/Frameworks/libqcadpolygon.dylib
0x109e7c000 - 0x109edffff org.qt-project.QtUiTools (6.4) <516ccc55-f406-3440-b0e8-9e02016a67db> /Applications/QCAD-Pro.app/Contents/Frameworks/QtUiTools.framework/Versions/A/QtUiTools
0x106508000 - 0x10650ffff org.qt-project.QtOpenGLWidgets (6.4) <41848e91-ab63-32f6-b910-fd0bb41ad833> /Applications/QCAD-Pro.app/Contents/Frameworks/QtOpenGLWidgets.framework/Versions/A/QtOpenGLWidgets
0x105440000 - 0x105447fff libconcavehull.dylib (*) <d837fe15-b71a-3baa-8e53-a5368e9a6340> /Applications/QCAD-Pro.app/Contents/Frameworks/libconcavehull.dylib
0x10a43c000 - 0x10a887fff libqcadpdf.dylib (*) <093902bd-646d-3997-a16d-f2f07180189c> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcadpdf.dylib
0x10b0a4000 - 0x10b7a7fff libqcadproscripts.dylib (*) <d8cdf77e-e618-3ae8-bb92-42999537eb7e> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcadproscripts.dylib
0x10c3ac000 - 0x10cf67fff libqcadscripts.dylib (*) <8018c668-8fb9-3b03-8a2e-ebae0dbc23c8> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcadscripts.dylib
0x109cc0000 - 0x109cd3fff libqcadshp.dylib (*) <ab708ab4-c3a9-3758-84fc-4f0ff08ff60d> /Applications/QCAD-Pro.app/Contents/PlugIns/libqcadshp.dylib
0x106524000 - 0x10652bfff libqgif.dylib (*) <fabce6ac-714a-3884-bd73-6faf33bbd4d2> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqgif.dylib
0x109d70000 - 0x109d77fff libqwbmp.dylib (*) <dc542b64-fd8e-30ba-864f-099d1e5a788b> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqwbmp.dylib
0x109d88000 - 0x109df3fff libqwebp.dylib (*) <275f6c12-b594-3ec1-8002-afae818a8deb> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqwebp.dylib
0x109e08000 - 0x109e0ffff libqico.dylib (*) <c39c4792-e821-3d0e-a51e-4c91092b2cbf> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqico.dylib
0x109e20000 - 0x109e27fff libqmacheif.dylib (*) <28e973af-8681-333a-8e06-ca0ef139c6f1> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqmacheif.dylib
0x10af88000 - 0x10afc7fff libqjpeg.dylib (*) <4a19d30b-c91f-3c5e-93e6-313b73aded30> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqjpeg.dylib
0x10afdc000 - 0x10b03bfff libqtiff.dylib (*) <ebd99856-9f3e-374d-adec-78591b8e5ecb> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqtiff.dylib
0x109e38000 - 0x109e3ffff libqsvg.dylib (*) <55448c8b-cdbb-3509-8e76-498a4e6909c1> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqsvg.dylib
0x109e50000 - 0x109e57fff libqicns.dylib (*) <fb8078bc-26e3-3404-9712-2820f6dccc99> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqicns.dylib
0x10a348000 - 0x10a34ffff libqtga.dylib (*) <ae8c892d-3d68-32e2-823e-02d20a1273ae> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqtga.dylib
0x10a360000 - 0x10a367fff libqmacjp2.dylib (*) <3a65cf03-f572-371d-813a-469eedc9151f> /Applications/QCAD-Pro.app/Contents/PlugIns/imageformats/libqmacjp2.dylib
0x1054a0000 - 0x1054abfff libobjc-trampolines.dylib (*) <80f14f3d-d099-3693-a8e0-eb9a526b1790> /usr/lib/libobjc-trampolines.dylib
0x10dc14000 - 0x10dc1ffff libqsvgicon.dylib (*) <59fc1d66-aaf2-3b22-8dd8-2eca5e04bf88> /Applications/QCAD-Pro.app/Contents/PlugIns/iconengines/libqsvgicon.dylib
0x113748000 - 0x113757fff libqcadcustomwidgets.dylib (*) <8f944d85-4001-384d-befb-d6c2c9fe74c2> /Applications/QCAD-Pro.app/Contents/PlugIns/designer/libqcadcustomwidgets.dylib
0x18e11f000 - 0x18e5f8fff com.apple.CoreFoundation (6.9) <b4fdaece-9727-3969-b014-27f7f24c8e01> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x18f0b8000 - 0x18fa7dfff com.apple.Foundation (6.9) <b7d67e5a-dce2-3f6b-b2b8-895a3669e3ec> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x191383000 - 0x192291fff com.apple.AppKit (6.9) <cc3e5215-4cd7-364c-8750-6eb7002720ce> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x192d9f000 - 0x1931c7fff com.apple.SkyLight (1.600.0) <e3d1dd9e-fa1b-332e-86ba-cc2915276118> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight
0x18df0c000 - 0x18df53fff libdispatch.dylib (*) <8e87dc0e-a570-3933-b37d-5e05ad516206> /usr/lib/system/libdispatch.dylib
0x1979a1000 - 0x197cd4fff com.apple.HIToolbox (2.1.1) <5f34bbf5-653a-31a5-b4b3-0a02c91ab488> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x18dd62000 - 0x18ddf053b dyld (*) <ac277a36-1808-327a-8761-cca585421212> /usr/lib/dyld
0x18e07f000 - 0x18e0b8fe7 libsystem_kernel.dylib (*) <7acbd9bc-d056-310e-858d-81b116cf6d28> /usr/lib/system/libsystem_kernel.dylib
0x18e0b9000 - 0x18e0c5fff libsystem_pthread.dylib (*) <b401cfb3-8dfe-32db-92b3-ba8af0f8ca6e> /usr/lib/system/libsystem_pthread.dylib
0x0 - 0xffffffffffffffff ??? (*) <00000000-0000-0000-0000-000000000000> ???
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=1.4G resident=0K(0%) swapped_out_or_unallocated=1.4G(100%)
Writable regions: Total=5.5G written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=5.5G(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Accelerate framework 256K 2
Activity Tracing 256K 1
CG backing stores 7680K 8
CG image 496K 22
ColorSync 624K 28
CoreAnimation 240K 15
CoreGraphics 48K 3
CoreUI image data 3584K 26
Foundation 48K 2
JS VM Gigacage 76.0M 19
JS VM Isolated Heap 23.2M 22
JS VM Isolated Heap (reserved) 2048K 1 reserved VM address space (unallocated)
Kernel Alloc Once 32K 1
MALLOC 3.1G 160
MALLOC guard page 192K 9
MALLOC_MEDIUM (reserved) 2.0G 17 reserved VM address space (unallocated)
MALLOC_NANO (reserved) 256.0M 1 reserved VM address space (unallocated)
STACK GUARD 56.3M 17
Stack 16.5M 17
VM_ALLOCATE 624K 28
__AUTH 1366K 290
__AUTH_CONST 21.2M 487
__CTF 824 1
__DATA 6428K 527
__DATA_CONST 30.6M 539
__DATA_DIRTY 1488K 168
__FONT_DATA 2352 1
__INFO_FILTER 8 1
__LINKEDIT 850.3M 51
__OBJC_RO 66.2M 1
__OBJC_RW 2011K 1
__TEXT 568.2M 554
dyld private memory 320K 4
mapped file 480.4M 47
shared memory 960K 19
=========== ======= =======
TOTAL 7.5G 3090
TOTAL, minus reserved VM space 5.3G 3090
|
|
2483 | QCAD (main) | Bug Report | Low | File > Open: MLeaders with text not imported | Assigned | |
|
Task Description
See also: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10159
|
|
2494 | QCAD (main) | Bug Report | Very Low | Information scrip on drawing screen unaligned. | Waiting on User | |
|
Task Description
Please view the attachment.
Regards
Graeme
|
|
2528 | QCAD (main) | Feature Request | Low | Add cycles (a.k.a. turns or revolutions) to the availab... | Assigned | |
|
Task Description
Hello, I recently bought QCAD Pro and this is my first Bugtracker report!
First, I want to say a big thank you for creating and maintaining such a wonderful software package!
I’ve never encountered a system for expressing constraints in 2D (or even 3D) that feels as natural, intuitive, and expressive as QCAD feels!
I am very grateful to have randomly found it somehow. I wish all user interfaces were designed this way and especially that vector art programs adopted similar constraint-based tools.
Anyway though, here’s the actual feature suggestion:
I noticed that QCAD is missing one especially convenient and naturally occuring angular unit: cycles (a.k.a. turns or revolutions).
I personally find cycles to be my favorite unit overall and to be the most intuitive to work with (when not needing to use physical protractors). I actually mostly work digitally and most of my uses for QCAD will be digital. QCAD is the only software I’ve found that really expresses 2D constraints the way I want to be able to work and lay things out.
Rather than redundantly belabor the many reasons why I think cycles should added to the available displayed angle units in the Preferences → Dimension Settings → Angular Dimensions dropdown list, I will simply link to the rather large discussion I’ve already had with Husky and CVH arguing my case about why I want it added and why many other users could benefit from it.
Here’s the link to the relevant forum discussion.
|
|
2529 | QCAD (main) | Feature Request | Low | Add normalized unit circle coordinates (complex numbers... | Assigned | |
|
Task Description
Similarly as for my previous suggestion submission, I also had a related idea for making it easier to work with complex numbers when using QCAD by adding normalized unit circle coordinates as another option in the Angular Dimensions display units options dropdown.
Here’s the corresponding forum thread I started.
|
|
2530 | QCAD (main) | Feature Request | Low | Make it possible to control the tooltip delay time when... | Assigned | |
|
Task Description
I noticed that every time I move my mouse from the main working canvas (schematic area) to the tool buttons on the left sidebar there is a delay before the first hover tooltip (which displays the tool names and hotkeys corresponding to each tool button) displays.
The tooltips remain fast (near instant) after that initial hover, but it it would be nice if there was an option field for controlling how long the tooltip delay is for that initial display delay.
Currently, on my Windows 10 machine, it takes about 1 full second for the tooltip to show, which may not sound like much but feels like a lot when trying to work faster.
Here is a link to the related forum discussion, which also discussed a different (and I’d say more useful/effective) idea as well.
I’m creating two separate Bugtracker submissions for that one thread though, to keep things clean.
Perhaps I should have created two separate forum thread for that to begin with.
|
|
2531 | QCAD (main) | Feature Request | Low | An always-visible hotkey overlay option would be extrem... | Assigned | |
|
Task Description
Hello! This is perhaps the most useful and valuable of the suggestion ideas I’ve had for QCAD so far!
I think it would be extremely useful if there was an option within the QCAD preferences for making it so that the hotkeys currently bound to each tool button in the UI (if existent) are always displayed such that they are overlaid on top of each of the buttons. There are two main approaches I can think of for doing that (both intended to avoid disturbing the existing layout of the UI):
Display the current hotkey binding associated by drawing it (probably in a distinct color) on one of the edges or corners of each of the buttons (such as the bottom middle side, the lower left corner, or the lower right corner). Even at a small font size I think this would be very effective and useful.
Instead of making the overlaid hotkey display in a small font at a side or corner of each button, you could have the hotkey text be in a large font and overlaid on top of the entire button, using things such as transparency and a distinctive (never used in the other parts of the UI) color to ensure that the button icons is still readable. A broader width of the font stroke may also help if transparency is used, so that the underlying icon lines remain more readable.
Both approaches have pros and cons. I personally lean towards the former, but Husky and CVH seemed to take issue with the readability of small fonts and so I later suggested the later option too.
They seemed opposed to both (at least during the forum discussion). However, I think this UI feature could be one of the best workflow speed improvements for the average user (many/most of whom probably don’t have time to memorize the hotkeys or just don’t end up doing so) of QCAD!
The gains in efficiency and pleasantness could be enormous potentially, even despite it QCAD already being among the most pleasant and well-designed programs I’ve ever used!
It is far faster to be able to instantly read a hotkey from the UI than to have to wait for a tooltip or to look the keystrokes up in the documentation.
Memorization is the fastest of course, but as someone who finds themselves constantly spread thin over many different programs (often half a dozen or more) for long spans of time I often find it difficult to remember all of the hotkeys for each program I use. Having such hotkeys always visible is useful for users who are spread thin, as many people increasingly in the world of software.
CVH suggested that I make custom icons myself, but doing so seems far worse than simply having QCAD automatically read and then print out the corresponding hotkeys over every tool in a programmatic and properly automated way.
I seriously think this would be one of the most awesome improvement you could ever add to QCAD!
Indeed, there is no missing feature I want more than this one!
Few programs do this but the few cases I’ve seen it the feature was extremely useful for speed without having to take weeks/months/years to fully memorize hotkeys only then forget them later. This idea eliminates that problem!
It would be glorious from a usability and accessibility standpoint! Please implement it!
Hopefully Qt’s GUI system is flexible enough to draw overlaid text over the buttons like this without to much hassle. That is the main potential impediment as I see it.
Anyway though, here is the associated forum discussion where I mentioned this idea. It was the same thread as the one where I also suggested adding a way to control tooltip delays.
|
|
2532 | QCAD (main) | Feature Request | Low | An "auto-tick" or "automated ruler creation" tool (adde... | Assigned | |
|
Task Description
Hey, this is the first of my feature suggestion submissions that isn’t tied to a corresponding suggestion thread on the QCAD forum.
Should I always create corresponding feature suggestion threads or is it ok (or better?) to just post ideas here?
Anyway though, here’s the idea:
I noticed that it is relatively easy to use things like the QCAD Split Entities and/or Paste Along Entity tool(s) to create an even set of divisions along a curve or line.
There’s also the Misc → Draw → Counter available too, for automated counting.
These together are useful for creating a “scale ruler” to be printed on a schematic for ease of reference or for use in cases where someone forgets to bring along a physical measuring device or when someone else is using that measuring device.
For example, one could print a to-scale 1 foot long ruler (or whatever other scale is relevant, e.g. 1 inch for small objects or just as a nice scale reference/legend/key) on the schematic page for convenience.
However, it would be nice if there was a convenient tool added to the Dimensions tool category that automated this entire process and was able to create arbitrary ruler-like numbered reference scales along lines (and even better if it also worked on arcs, though less important).
Even better would be if this “auto tick” or “auto ruler” tool supported multiple levels of tick scaling (e.g. 2 or 3) such as what one sees on actual rulers.
For example, an imperial ruler for a foot (I’m in the US currently) will typically having increasingly smaller tick marks added at halfway points between each of the numbered points along the ruler’s scale, which makes using it quickly much easier. For example, it’ll have a half-length tick for half an inch and then a quarter-length tick for each quarter of an inch within an inch (with the inch’s ticks being full length).
It seems like it could be relatively easy to implement that kind of nested tick marking system, which would make it super convenient and pleasant for the user of QCAD to create usable to-scale ruler-like objects wherever they desire them with hardly any effort!
I think this idea would also fit extremely well with existing tools in the Dimensions category and would be useful for many/most QCAD users!
It’s yet another good QCAD feature that could attract more people to buy upgraded copies of QCAD in the future I think!
I hope you implement it. Small conveniences still make a big difference.
Anyway, thanks a bunch again for creating this awesome program!
That’s all the suggestions I have for today.
I hope you have a wonderful weekend and upcoming week, etc!
|
|
2533 | QCAD (main) | Bug Report | Low | Surveyor's units never seem to display when selected as... | Assigned | |
|
Task Description
I've tried several times to try to see what the "surveyor's units" option of the Angular Dimensions format in the UI preferences will display as, but all it ever seems to do is cause the angle measurement to become blank. No angles are displayed whenever this mode is selected.
Indeed, I cannot figure out what the setting actually does besides causing angles to never be displayed.
Is there a way to make this setting do something meaningful or is it just broken?
I found an old forum thread from 2016 about this same issue and it sounds like the same things is still happening since then.
I'm not a surveyor so I have no actual practical use for these units that I can yet see, but I just figured I'd add an report to the bug tracker here in case any developers aren't aware that the bug still seems to exist.
Does the setting do anything besides changing the displayed units in the status bar?
|
|
2535 | QCAD (main) | Feature Request | Low | New tool idea: Scale polyline objects separately, each ... | Assigned | |
|
Task Description
In my current QCAD file I’m working on, I have a circular hub with a hole in it which I am also trying to place an alternating sequence of rectangular spokes of a certain relative size around.
I had 4 spokes that I had copied and rotated 45 degrees to create 8 spokes in total around the circle. I tried scaling the the non-cardinal spokes relative to the center of the circular ring, but that causes them to also move towards the center of the ring as they shrink, thereby putting them out of place as they scale.
I therefore had to activate the scale tool once per each object and set an origin (focus) point around the area where each spoke is “attached” to the ring in order to stop each from shifting inward to the circle as it scales.
It occurred to me though that there could be a simple tool or option to do this without that.
Each of my rectangles are polyline objects and thus are coherent continuous objects.
A new scaling tool could be designed such that it is based on simply clicking on each scaling origin on each object (using snapping tools if needed) and then clicking a check button (or enter) when done and then causing the scaling GUI to appear so the user can specify the desired scaling. Each scaling would then be applied to where the polylines were clicked instead of to all the objects as one.
This would be a much faster way to rescale a bunch of objects around individually varying relative scaling origins!
|
|
2536 | QCAD (main) | Suggestion | Low | The little circle that shows the error location when us... | Assigned | |
|
Task Description
I was having some problems getting some shapes to fill with a solid fill and was frustrated by the awkward numeric coordinate it was giving me for where the error (the disconnected shape points) were, until I fortunately noticed that a tiny pale circle appears around the point where the error is for about just 1 second.
This is a very helpful error indicator circle but is far too easy to miss.
Perhaps making it last longer (or letting the user control that) would be beneficial.
I also wonder if showing multiple such circles (when they exist, as they did in the piece I was working on) at the same time or having that as a UI option would be good.
Anyway, goodnight all!
|
|
2537 | QCAD (main) | Feature Request | Low | More variants for converting element types could be use... | Assigned | |
|
Task Description
I don’t actually have any use for this idea currently, but am just posting it here to document it for consideration.
Basically, it occurred to me at least a few more useful conversions between shapes besides the existing ones could be useful.
For example:
Converting lines into axially aligned rectangles of a specified “radius” or “diameter” (with an option to delete or keep the original line geometry).
An option for the above (lines –> rectangles) that causes the intersections between the resulting rectangles to be automatically removed, like a kind of “automatic/magic wall creation tool” based on laying down lines instead of rectangles and then converting via this tool.
Converting circles/ellipses and rectangles back and forth between each other via their bounding volumes. It seems reasonably likely that people will sometimes want to convert circular design elements into rectangular ones and vice versa (e.g. deciding a rectangular column makes more sense than a cylindrical one and vice versa).
Converting any arbitrary selection into a corresponding bounding circle (not rectangle, which already exists) of sufficient size to enclose all points in the selection.
Basically, QCAD already has tools for converting shapes with operations that are a natural fit for the existing geometry, but has less tools for converting to entirely different geometry, but such uses could actually still be very useful potentially!
It seems likely to be common enough as a use case to merit inclusion, rather than just using scripting.
I don’t have any pressing need for these and I know that I could script them to create them if I really wanted to.
These are relatively minor ideas. I’m just putting this out here as more ideas for making this already wonderful software even better. :)
|
|
2552 | QCAD (main) | Suggestion | Low | Keep Windows menu shortcuts (Alt+Key) unique per menu | Assigned | |
|
Task Description
Reason: Same underlined keys are used for different menus
Select and Snap = S, Dimension and Info = I, Modify and Misc = M,
|
|
2555 | QCAD/CAM | Suggestion | Low | Include tool description when selecting a tool. | Assigned | |
|
Task Description
Andrew,
At present QCAD/CAM the tool drop-down box displays tool number and diameter between brackets.
It would be more appropriate to display if it is a mill or a drill and/or the description of such. In a further stage of development ball-nose ... Conical ... And so on.
I have several specialized mills with the same diameter. End-mills, roughing mills, routing mills, face mills ....
Tools 1(ø6mm) or 2(ø6mm) don’t say much if tool 1 is a side-mill and tool 2 is a high speed drill for metal.
Related forum topic: https://www.qcad.org/rsforum/viewtopic.php?f=31&t=10722
Regards, CVH
|
|
2556 | QCAD (main) | Bug Report | Low | Win11 Printing Orientation Issue: Landscape >>Portrait | Assigned | |
|
Task Description
Andrew,
Related topic: https://www.qcad.org/rsforum/viewtopic.php?f=33&t=10649
Already two different users report that Landscape is printed cropped in portrait format, both Win11. The behavior change occurred recently. Although the second user (rdtsc) reports the same behavior for latest Mabox Linux (Manjaro, Arch.)
Can not replicate that on Win7 32 bit nor on Win10 64 bit, both are no longer or not updated OS. For one, I have no orientation setting displayed in my printer dialog.
It seems not to be related to the QCAD version: Reported for: - Win11 QCAD Pro 3.29 - Win11 QCAD-CAM 3.27.8.0
Regards, CVH
|
|
2557 | QCAD/CAM | Suggestion | Very Low | G20/21 not occuring in generic postprocessors | Assigned | |
|
Task Description
Andrew,
I know that GCodeMM.js and GCodeIN.js are generic postprocessors. Mostly used as base for other or custom postprocessor.
The distinct nature is pretty clear from the filename and the suffix in the display name. Another distinct nature is that they include this.unit = RS.Millimeter / RS.Inch intended for the CAM side.
Why don’t they include at least a G20/21 in a generic header?
There are several more specific postprocessors where I miss these G-codes for the measurement system.
True, if they are not supported, no error messages would occur when omitted. The danger is that users rely on build in postprocessors hoping that it matches with the default measurement system of their setup.
IMHO it is safer to trigger an instruction fault before attempting to execute a wrong motion. As fail-save as possible should always be the goal.
Regards, CVH
|
|
2558 | QCAD/CAM | Bug Report | Low | Offset trajectory path issue with circular Lead In/Out | Waiting on User | |
|
Task Description
Andrew,
Please refer to related forum topic: https://www.qcad.org/rsforum/viewtopic.php?f=74&t=10724#p44206
An eighth circle with radius 8 Lead In/Out relates to nothing in the actual exported cutter trajectory. Nor does it with the edge being cut.
Proper examples and a comparison with ‘Extension’ type Lead In/Out included. Conclusion: IMHO connecting the cutter trajectory and edge being cut is wrong.
It looks a lot like turning on Cutter Compensation (G41/42) while the motion is circular. But that is uncommon because most controllers can not cope with this motion. One can increase the offset gradually along a straight pre-entry segment for turning on G41/42 but not along a circular path. Also see snippet: - Pre-entry C→B turning on G41 - Circular Lead In B→A
Regards, CVH
|
|
2564 | ECMAScript | Bug Report | Low | REllipse::getVectorTo(p) returns a vector to a major po... | Assigned | |
|
Task Description
Andrew,
If a given point p is on the major axis then REllipse::getVectorTo(p) returns one of the major points. In the code this is handled as a special case when the point is in-line (collinear) with the major axis. This is only correct for points p outside the ellipse. Or better: For points p outside the area between the focal points.
The correct solutions are: - if p equals the center ⇒ two vectors to the two minor points. - if p equals one of the major points ⇒ the major point itself. - if p is in between the focal points ⇒ two vectors mirrored over the major axis. - if p is on the unlimited axis but outside the focal points ⇒ the nearest major point.
The problem is now what to return on a duality with full ellipses. Or for an ellipse arc where two results are valid.
For example: RCircle::getVectorTo(p) returns an invalid vector when the point is near the center. Then there are an unlimited number of solutions.
Further discovered that the point related to the returned vector may fail x²/a²+y²/b²=1 Although almost on the ellipse within 2.299e-10 ... f(x,y) may return 9.5310 This example would fail REllipse::contains while the border is considered as inside.
Meanwhile implemented a ‘simple method’ to find the nearest point(s) on an ellipse. Fast converging in 3 steps, no trigs and very accurate, about 24 lines of code. f(x,y) returns mostly 1.000 with so far: - a minimum of 0.9999999999999997 - a maximum of 1.0000000000000007. In other words, it is only off for the last meaningful decimal digit.
With this all methods that are based on REllipse::getVectorTo(p) can be implemented very reliable with tolerance, border flag, ... and so on. By default the normal for a point is given with high accuracy and a tangent is that rotated. ... .. .
Regards, CVH
|
|
2565 | QCAD (main) | Bug Report | Very Low | NaN length for arbitrary ellipse arc | Assigned | |
|
Task Description
Andrew,
Probably not OS or QCAD version related.
The ellipse arc in the example file is drawn CCW and then the start parameter was set to 180. (All part of a test of newer code for the nearest point on an ellipse) Its end parameter was originally 44.56263613...
If we reload this file its properties are: - Not reversed (CCW) - ratio is 0.42307692... - Parameters are 180 & 404.56263613... - The reported length is about 1993.21829743...
To replicate the issue you must draw over this ellipse shape: - EA ; Direction CCW - SR for snapping to references. - Indicate the major, minor, start and end point all by snapping to the original references.
You now have a copy of the provided ellipse shape. Select it with Alt-Select, it is the one without a length.
Properties are: - Not reversed (CCW) - ratio is 0.42307692... - Parameters are 180 & 44.56263613... - The reported length is NaN
I can replicate that for some other CCW ellipse arcs ... ... Perhaps given that the start parameter is 180 degrees. Also suspecting that it can be replicated for CW arcs.
For the record: A 2D wire Centroid for this shape also fails. Simply because it tests for the length reported by QCAD. It doesn’t start to approximate something that is about zero long.
Regards, CVH
|
|
794 | QCAD (main) | Bug Report | Low | Applying Solid grid lines - not working | Assigned | |
1 |
Task Description
Windows 3.0.8 Application preferences > Graphics View > Appearance - Solid grid lines doesn’t change anything?
|
|
173 | QCAD (main) | Feature Request | Low | explode text to letters | Assigned | |
1 |
Task Description
implement
|
|
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.
|
|
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?
|
|
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.
|
|
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.
|
|
584 | QCAD (main) | Bug Report | Low | Library Items können unbrauchbar gemacht werden durch l... | Assigned | |
1 |
Task Description
Nach einigen Überraschungen ....
Es ist möglich Layer in nicht eingefügten oder unsichtbar geschalteten Library Items unbemerkt zu löschen ....
Fallbeispiel 1: Ich arbeite an einer Zeichnung die u.a. den Layer “Gelbe Linie” benutzt. Ich füge ein Library Item ein was auch einen Layer “Gelbe Linie” hat. Ich lösche - aus welchen Gründen auch immer - in der Zeichnung das Library Item weil ich es erst später wieder verwenden will. In der Blocklist ist es natürlich immer noch verfügbar. In der Zeichnung lösche ich den Layer “Gelbe Linie” da ich diesen nicht brauche brauche - habe aber natürlich nicht im Kopf welche Layer in meinen Blocks verwendet wurden. Nach einiger Zeit will ich den Block (den aus der Library) wieder einfügen - dieser ist nun aber unbrauchbar da der Inhalt welcher auf dem Layer “gelbe Linie” war fehlt. Das Library Item neu aus Library laden um das bereits existierende zu reparieren scheitert da das erste nicht überschrieben werden kann. Ich muss den ersten Block löschen um den neuen benutzen zu können.
Fallbeispiel 2: Da das selbe (löschen der Layer) auch passieren kann bei unsichtbar geschalteten Blöcken kann es dazu führen das ich zig bereits positionierte Blöcke zerstöre und neu platzieren muss um meine Zeichnung zu reparieren.
Fallbeispiel 3: Ich sehe in meiner Zeichnung einen Layer “Gelbe Linie”. Weiß nicht was das ist - schalte alle Layer unsichtbar außer “Gelbe Linie”. Klicke auf “Auto Zoom” um zu sehen was den auf “Gelbe Linie” ist. Finde nichts = also leer! Lösche Layer “Gelbe Linie”. Der Layer wurde aber von einem im Moment nicht verwendeten Library Block verwendet. Es gibt keinen Hinweis das ich damit ein Library Item zerstören könnte ....
Lange Rede kurzer Sinn: Wäre es machbar/sinnvoll Layer in Blöcken nur löschen zu können wenn ich mich im Edit Modus der Blöcke befinde?
|
|
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.
|
|
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
|
|
609 | QCAD (main) | Feature Request | Low | Clean up tool | Assigned | |
1 |
Task Description
To have a ‘clean up ' tool to:
- eradicate duplicate lines - eradicate stray points - remove empty layers - remove unused blocks
Perhaps with an initial dialog which allows the user to choose what they want to clean up.
|
|
612 | QCAD (main) | Feature Request | Low | Plot math functions | Assigned | |
1 |
Task Description
Input:
X axis min/max or choose line (?) or center (for polar functions)
function: y = f(x) / polar function: r = f(a)
Output:
function plot
|
|
625 | QCAD (main) | Feature Request | Low | Distribute block along spline, polyline, ... | Assigned | |
1 |
Task Description
See: http://www.youtube.com/watch?v=27bCgg3zLVA
|