|
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]
|
|
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 |
|
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.
|
|
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.
|
|
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
|
|
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?
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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 )) ?
|
|
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
|
|
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?
|
|
604 | QCAD (main) | Feature Request | Low | Measure and record X,Y coordinates tool - add to info ... | Assigned | |
|
Task Description
Feature request See topic - http://www.ribbonsoft.com/rsforum/viewtopic.php?f=31&t=2015
Just a thought, but one that could be useful for machinists in particular - a measurement tool that can snap to a point as per usual, but then just displays the drawing coordinates in X and Y. This could be expanded to the dimensions tool set, so that you can click on a point and print the coordinates next to it.
|
|
614 | QCAD (main) | Feature Request | Low | Blocks - overwrite current layer yes/no ... | Assigned | |
|
Task Description
I would appreciate an option for the library Browser that gives me the possibility to decide by my self to use the current (same name) layer in my drawing or overwrite it with the existing layers in the library item.
Imagine the possibility’s of this feature ....
|
|
617 | QCAD (main) | Feature Request | Low | Different dimensions font sizes in the same drawing. | Assigned | |
|
Task Description
Different dimensions font sizes in the same drawing.
|
|
622 | QCAD (main) | Feature Request | Low | Disproportianal scaling of arcs, ellipses | Assigned | |
|
Task Description
Support disproportional scaling also for arcs, ellipses, other entities, not only lines and polylines with only line segments.
|
|
628 | QCAD (main) | Feature Request | Low | Improve workflow for entering tool parameters | Assigned | |
|
Task Description
Provide keyboard shortcuts for options tool bar.
Under Linux, Windows Alt+Key shortcuts can be used. Mac OS X does not seem to support this.
See also suggestions at: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=32&t=2053&view=unread#unread
|
|
631 | QCAD (main) | Feature Request | Low | Option "Scale" für das öffnen von Templates ... | Assigned | |
|
Task Description
Wenn ich eine Zeichnung plane überlege ich mir natürlich im Vorfeld welche Blattgröße und welchen Maßstab ich verwenden möchte.
Wenn ich Templates (z.B. Zeichnungsblatt A4) für die Blattgröße öffnen könnte und dabei direkt einen Skalierungsfaktor (z.B. 10) vorgeben könnte hätte ich ohne Umwege gleich alles was man braucht. In diesem Fall ein A4 Blatt im Maßstab 1:10.
Im Grunde genommen das selbe was ich bereits mit Library Items machen kann ...
|
|
637 | QCAD (main) | Feature Request | Low | Viewports / View List | Assigned | |
|
Task Description
1. The Scrollbars for each window in the Viewports has the same size like the normal used scrollbars for windows. If you are working on a normal size Monitor it “steals” a lot of “working space”. Is there any possibility to make the scrollbars smaller or just a line to separate the windows so that I have to navigate with Keyboard and mouse?
2. I thing the Viewports and the View List belongs together - is it possible to get a button in the “View List / Tool Bar” to choose a Viewport style instead of “walking” the long way over the “Drawing preferences” Menu?
See also: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=47&t=2071
|
|
639 | QCAD (main) | Feature Request | Low | Ability to load a file of keyboard shortcuts | Assigned | |
|
Task Description
It would be useful if a file of keyboard shortcuts to commands could be loaded.
Then a set of shortcuts identical/based on the Autocad keyboard shortcuts can be loaded, making it much easier for Autocad users to migrate to your product.
There does seem to be some future functionality planned here, with the shortcut ‘scheme’ selector in Program Preferences, but for the moment ‘Qcad’ is the only option available.
This strategy is used to great effect by Draftsight (but who trusts a big company like Dassault/Solidworks...)
|
|
648 | QCAD (main) | Feature Request | Low | Configurable behavior for line patterns at weight 0.00 | Assigned | |
|
Task Description
A line with linestyle = dots and line weight = 0.00 appears in model space overly spaced, all other lineweights behave as expected. Suspect other linestyles to behave in a similar fashion.
See attached drawing.
Suggested fix: use the same scaling for lineweight 0.00 as for lineweight 0.05.
|
|
661 | QCAD (main) | Feature Request | Low | Add support for the DGN format | Assigned | |
|
Task Description
See OpenDesign news: “ODA consolidates support for .dgn and .dwg file formats in Teigha”
|
|
674 | QCAD (main) | Feature Request | Low | To add optional 'auto' dimension tracking feature. | Assigned | |
|
Task Description
It might be useful for some to have the option to turn on/off ' auto’ dimension tracking option.
See related topic: http://www.qcad.org/rsforum/viewtopic.php?f=2&p=6893#p6893
|
|
675 | QCAD (main) | Feature Request | Low | Option for fixed Text and Dimension heights ... | Assigned | |
|
Task Description
I think it would be nice to have the possibility to decide a fixed Text and Dimension (inclusive Arrows) height what is not affected by the Print scale. That means: If I have a given height of 3,5mm it will always be printed with 3,5mm - no matter what the scale for the printing is. Yes, I see also the problem that I could run in space problems after I twitch to the Print preview - but that will also happen when I change the Text hight in the preferences for a 5:1 printing. Maybe this Feature Request doesn’t looks important if you are usually working with Metric Units but if you have to handle Imperial Units then it is a pain in the back to make always the calculation to get the same heights. Try it by your self; 3,5mm = 0.137795” = 1”:1” Now I like to print it in 1”:256” ops - to small - ok 1”:64” ... no, to big, maybe 1”:128” .......and QCad can’t remember the previously numbers.
|
|
680 | QCAD (main) | Feature Request | Low | Additional Export function for Sketchup etc. .... | Assigned | |
|
Task Description
Additional Export function for export/import into 3D Programs like Sketchup etc. (file types like .dae, .3ds, .ddf, .skp).
See also: http://www.ribbonsoft.com/rsforum/viewtopic.php?f=32&t=2176
|
|
719 | QCAD (main) | Feature Request | Low | Library Browser additional Function ... | Assigned | |
|
Task Description
It would be nice to get:
In the Create Library Item task → “Save as” a remember Function for the last chosen Path to save the Item ... or a default path what is the same like the settings in the Application Preferences. Right now you have to navigate again and again for every item what you will save in the same directory. If you have to save 20 items - it sacks
Also would it be nice for an easy “Clean up” to have the possibility to delete items directly in the Library Browser window. Right now you have to use extern Programs like the Windows explorer to move or delete items.
|
|
747 | QCAD (main) | Feature Request | Low | DXF import: dimension label | Assigned | |
|
Task Description
Add support for custom dimension labels created in 3rd party applications. Such labels may contain text that is stripped by QCAD.
|
|
783 | QCAD (main) | Feature Request | Low | Save as .dgn option missing in 3.0.8? | Assigned | |
|
Task Description
Not really a bug I suppose but the save as.dgn file format is missing in snapshot 3.0.8 release.
Will this be available again soon?
|
|
787 | QCAD (main) | Feature Request | Low | Hatch generator - plug in tool? | Assigned | |
|
Task Description
Would it be possible to make a Plug in tool for a Hatch generator, so custom made hatches can be saved as .pat files?
I have a lot of up and coming future projects that I would like to make my own ‘custom’ hatches for.
|
|
792 | QCAD (main) | Feature Request | Low | New 'Match' properties tool | Assigned | |
|
Task Description
To add a new ‘Match’ properties tool.
For example, I have a large drawing with lots and lots of entities on various layers and I want to select some entities (say 500 or more) which are all on different layers and change all these selected entities to match the properties of one other particular entity - but, but I want the ‘Matched’ entities to remain on their own layers.
OK, of course I can use the property editor for this and this is fine in most instances but I would first need to determine the the layer data for the properties of the entity I would like to match to (Color, Line weight and Line type) in the first place and then I need to remember these attributes in order to change things in the property editor in order to change all of my selection to match!
As I say mostly the above procedure would be fine to use but for convenience it would be great to have a new tool to do all this for me and cut out a few steps in the process.
A new ‘Match’ properties tool procedure could be something like this:
1. Select Match properties tool.
2. Select all entities to be matched.
3. Select entity to match to.
4. Tick or leave un-ticked - move to same layer.
5. Complete process.
* Actually, while writing this I`ve just thought of another useful addition which could be added to the Info tool set, ‘Entity’ properties info! Example - click on Info > Entity Properties and click on the entity in question and then the properties are displayed without going to the layer data for this! Just an idea ;)
|
|
802 | QCAD (main) | Feature Request | Low | User defined toolbar | Assigned | |
|
Task Description
It would be a nice feature to be able to define your own toolbar.
See: http://www.qcad.org/rsforum/viewtopic.php?f=32&t=2393
|
|
805 | QCAD (main) | Feature Request | Low | Create tool radius compensation / tool path generation | Assigned | |
|
Task Description
This is how I would implement this:
This would be a modification tool. Parts are selected, a toolpath is generated, and a dialog pops up to allow putting the tool path into an existing layer, a new layer, or replace all drawings in an existing layer.
This is how the toolpath is generated:
We iterate through all elements and explode everything but text into line segments. Then we connect the line segments into chains wherever the line endpoints are less than some tolerance away from each other. The chains can be very chaotic, but at least we have separate entities for now.
For every chain, we need to find the largest complete loop. A good drawing would only contain non-overlapping loops, but we can’t expect that. Everything that is not on this loop can not be defined as a part or as a hole, so we will merely create a tool path segment that is equivalent to the line segment. Every segment that *IS* on a loop is either an outside edge (part outline), or an inside edge (hole outline), (or overlapping, in which case it is neither, and we have an operator problem).
In a perfect world, we need to find exactly which shape is inside which other shape, and then create alternating tool offsets from the outmost loop (part edge) to the second outmost (hole), to the next (part) etc. .
In a simplified world, we can used the bounding box of the loop instead. This works OK for rectangular shapes, but a circle next to an “L” shape could be seen as inside the L’s bounding box, hence inside the L, wrongly accused of being a hole, not a part.
Now all that is left to do is to create a new loop, offset by the tool radius. Oh, and since we have the connections from line segment to line segment in the correct order already, we can use the opportunity to order all cutting loops from inner to outer, or from small to large, and order non-loop edges by travel distance.
The new drawing in the new layer can now be exported without further hassle to create a nice laser cut file.
PS: of course, a user could create multiple layers for marking, cutting, enraging, etc. . Additional Layer attributes for cutting speed and laser power (and a few more) would be needed.
|
|
813 | QCAD (main) | Feature Request | Low | New Snap tool: Isometric coordinates ... | Assigned | |
|
Task Description
It would be nice to have an additional Coordinate tool for isometric constructions.
If I’m working on an isometric drawing I have to design my things with x, y, z coordinates. Y is, of course not a problem but for x and z I have most off the time to work with construction lines for move, copy, locate etc. With an isometric coordinate snap tool what will follow the 30° angles for x and z we could save a lot of construction lines
|
|
817 | QCAD (main) | Feature Request | Low | Snap and cut all intersection in a given area tool ... | Assigned | |
|
Task Description
As we all know - from time to time - it is a lot of work to prepare a part of a drawing for a hatch. To get rid of one of the basic task (cutting lines along the desired hatch boundary) it would be nice to have an add-on - or what ever - what would cut ALL intersection in a drawing (or just on one layer, or just based on a selection etc.) with just a mouse click. Then it would be much faster and easier to do the selection for the hatch boundaries. The user could decide to make it directly in his drawing or he like to duplicate the drawing to an extra layer where this function will be used ....
Clive mentioned on this: Maybe a tool like this could be an additional ‘Snap’ selection option - select all snap intersections or select snap intersections within a boundary! then as you suggest ‘cut’ at the intersection points.
|