Can't edit paths or create notches in macOS Big Sur 11.6

[MissMuriel]

@Douglas

So are you saying that the items in the context menu of the posted image are NOT selectable?

Yes. They are not selectable.

@Douglas

Also if this is the case what do other context menu do… such as right clicking on a point in draft mode?

That works fine. I did not encounter any problems until I reached the “Add Details” stage.

@Douglas

BTW… what build ver of Seamly2D did you try in Big Sur? Apparently some BigSur issues were resolved with Qt 5.15.2 which we recently switched Seamly2D to.

I am using :

[MissMuriel]

But: This is the version I used on Catalina:

Wheras on the Mac with Big Sur, I used:

[Douglas]

@MissMuriel

That works fine. I did not encounter any problems until I reached the “Add Details” stage.

Ok… got an idea what you’re using… I’ll try and take a look and see if I find anything that might be causing just that context menu to hang.

BTW… I’m not a Mac user so excuse my ignorance, but I noticed the odd placement of the trash icon - is this normal for a Mac? In Windows or Linux the menus look like this - where the (trash) icons / checkmarks are all in a col on the left.

[MissMuriel]

@Douglas

BTW… I’m not a Mac user so excuse my ignorance, but I noticed the odd placement of the trash icon - is this normal for a Mac? In Windows or Linux the menus look like this - where the (trash) icons / checkmarks are all in a col on the left.

I checked in both app-versions. In both the trash is placed to the right of the column.

[Douglas]

@MissMuriel

I checked in both app-versions. In both the trash is placed to the right of the column.

Ok. Thanks. Guess it must be normal then and not a concern for running under Big Sur.

[Douglas]

@ MissMuriel

Hi Muriel

I took a look at the code in the section for the Workpiece dialog, and I don’t see anything that should be out of the ordinary. I have read a report of the same issue elsewhere, so it may be Qt / MacOs issue. There is maybe one thing I can see that might be causing the issue, but if that’s the case I would expect the same behavior with a couple other context menus.

If maybe you could check these menus as well I could rule in / out my suspicion… either the Group Manager or Pattern Piece dock areas:

If these work, then I’m at a loss at this time for the cause of the issue.

That being said… I may have misunderstood, but have you tried to open the Path context menu, then using the up down keyboard arrows to highlight an item, followed by to select / toggle the item?

[MissMuriel]

Wow Douglas,

Thank you for your time with this!!

And I’m happy to report we have a breakthrough, so let’s dive in:

@Douglas

If maybe you could check these menus as well I could rule in / out my suspicion… either the Group Manager or Pattern Piece dock areas:

To begin with:

These work fine. No problems here.

Now for the issue:

Like I described before, in the Path context menu, I can select a node by clicking on it with the mouse, and when I Right-click, the little menu for that node appears. I can move the selected node up and down the path with either the mouse or the arrows in the path-menu window, but I can’t use the mouse to select/unselect the menu-items.

But when the little menu is open, I can use the keyboard arrows to select one of the three options, and by clicking ENTER, I can invert the selection.

In the previous version I could do all that with the mouse, but for now I’m happy it works in some way, because it’s much easier to use the software on the iMac than on the laptop.

Thank you for showing me the light!

Muriel

[Douglas]

@MissMuriel

These work fine. No problems here.

Hmmm. Like I said, now I’m baffled. These context menus are constructed in the same manner as the Workpiece paths context menu using the same method of grabbing the current mouse position. Other menus use a couple different methods to find & map the mouse position… which I thought might be the source of the issue. In an odd sense I was hoping that was the case.

@MissMuriel

In the previous version I could do all that with the mouse, but for now I’m happy it works in some way, because it’s much easier to use the software on the iMac than on the laptop.

Well, I’m glad we figured out something and have a work around.

[AndrewBuck]

For what it is worth I can say I see the exact same behaviour on Mac OS 10.13.6 (High Sierra). I can use the mouse to open the context menu and do the selection on the group manager, but when operating on the ‘main path’ tab of the detail editor I can use the mouse to open the context menu but must use the keyboard to actually select something in the menu. If I try to click on something in the context menu, the context menu stays open and the computer ‘dings’ the little bell thing like you clicked on an option that was disabled.

[konrad]

Same issue here.

Both with

• Seamly2d 0.6.0.1 (12.10.2020) build revision Git:ec5a06f; Qt Version 5.13.2. Clang 11.0 (Apple)
• Seamly2d 0.6.0.1 (2.6.2018) build revision Git:12b271be4; Qt Version 5.11.0 Clang 8.1 (Apple)

this menu works perfectly fine.

With

Seaml2d 0.6.0.1 (7.2.2022) build revision Git:017bf92; Qt Version 5.15.2 Clang 13.0 (Apple)

it does not work anymore. I don’t have any releases between the enlisted 2020 and 2022 one, so it broke inbetween those two releases.

[Douglas]

@konrad

it does not work anymore. I don’t have any releases between the enlisted 2020 and 2022 one, so it broke inbetween those two releases

I believe the Mac issues might have arose with the recent switching to use Qt ver 5.15.2 and MSVC instead of the previous ver of 5.12.xx and GCC or whatever it was at the time.

I’m sorry I’m at a disadvantage as I don’t own a Mac to be able to test build with. I may just create another fork, and create another workflow to use an older ver of Qt for a Mac build - which will create a bunch of deprecation warnings - but it could validate if the Qt ver is indeed the problem. Of course one of you Mac users would have to check it out. Let me see what I can do…

[konrad]

@Douglas Happy to test a build once it is ready.

[Karu]

i work on mac as well. i have faced this problem too. additionally now the app crashed when I want to use my measurements in an fx I am able to open the measurements table by clickeg on “edit current” under “Measurements” but when I want to use it in fx to add a point, then it crashes

---

Translated Report (Full Report Below)

Process: Seamly2D [27281] Path: /Applications/Seamly2D.app/Contents/MacOS/Seamly2D Identifier: org.seamly2dproject.Seamly2D Version: 0.6.0 (0.6.0.1) Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 502

Date/Time: 2022-12-07 06:13:21.0422 +0530 OS Version: macOS 12.5.1 Report Version: 12 Bridge OS Version: 6.6 (19P6066)

Time Awake Since Boot: 720000 seconds Time Since Wake: 507 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY

Application Specific Information: abort() called

Application Specific Backtrace 0: 0 CoreFoundation 0x00007ff80b4d37c3 __exceptionPreprocess + 242 1 libobjc.A.dylib 0x00007ff80b233bc3 objc_exception_throw + 48 2 CoreFoundation 0x00007ff80b4d362a +[NSException exceptionWithName:reason:userInfo:] + 0 3 AppKit 0x00007ff80e7136fa _NSRunModal + 152 4 AppKit 0x00007ff80e2b8aa8 -[NSApplication runModalSession:] + 241 5 libqcocoa.dylib 0x0000000104275ed6 qt_plugin_instance + 194678 6 QtCore 0x000000010530cacf _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 431 7 QtWidgets 0x0000000103a40e9e _ZN7QDialog4execEv + 526 8 Seamly2D 0x0000000102851dfc _Z22noisyFailureMsgHandler9QtMsgTypeRK18QMessageLogContextRK7QString + 5820 9 QtCore 0x0000000105135e10 _Z17qt_message_output9QtMsgTypeRK18QMessageLogContextRK7QString + 256 10 QtCore 0x0000000105135d1d _Z17qt_message_output9QtMsgTypeRK18QMessageLogContextRK7QString + 13 11 QtCore 0x0000000105241fb8 _ZN6QDebugD2Ev + 104 12 libqcocoa.dylib 0x00000001042c0995 _ZN20QCocoaSystemTrayIcon17statusItemClickedEv + 198565 13 QtGui 0x00000001045ecc30 _ZN13QFontDatabase8findFontERK8QFontDefi + 720 14 QtGui 0x00000001045ef4fa _ZN13QFontDatabase4loadEPK12QFontPrivatei + 3210 15 QtGui 0x00000001045c2103 _ZNK12QFontPrivate15engineForScriptEi + 451 16 QtGui 0x00000001045f6138 ZNK11QTextEngine10fontEngineERK11QScriptItemP6QFixedS4_S4 + 1128 17 QtGui 0x00000001045f46d8 _ZNK11QTextEngine9shapeTextEi + 664 18 QtGui 0x000000010460d0f5 _ZN9QTextLine13layout_helperEi + 805 19 QtWidgets 0x00000001038bc51d _ZNK19QCommonStylePrivate19calculateElidedTextERK7QStringRK11QTextOptionRK5QFontRK5QRect6QFlagsIN2Qt13AlignmentFlagEENSD_13TextElideModeEibP7QPointF + 1581 20 QtWidgets 0x00000001038bc7dc _ZNK19QCommonStylePrivate12viewItemSizeEPK20QStyleOptionViewItemi + 508 21 QtWidgets 0x00000001038bca9d _ZNK19QCommonStylePrivate14viewItemLayoutEPK20QStyleOptionViewItemP5QRectS4_S4_b + 109 22 QtWidgets 0x00000001038c4942 _ZNK12QCommonStyle14subElementRectEN6QStyle10SubElementEPK12QStyleOptionPK7QWidget + 1154 23 libqmacstyle.dylib 0x0000000103797ed7 qt_plugin_instance + 67607 24 QtWidgets 0x00000001038bfe43 _ZNK12QCommonStyle11drawControlEN6QStyle14ControlElementEPK12QStyleOptionP8QPainterPK7QWidget + 8467 25 libqmacstyle.dylib 0x00000001037925d5 qt_plugin_instance + 44821 26 QtWidgets 0x0000000103ad451c _ZNK19QStyledItemDelegate5paintEP8QPainterRK20QStyleOptionViewItemRK11QModelIndex + 124 27 QtWidgets 0x0000000103aff6c6 _ZN10QTableView19setHorizontalHeaderEP11QHeaderView + 5638 28 QtWidgets 0x0000000103b00fd6 _ZN10QTableView10paintEventEP11QPaintEvent + 2102 29 QtWidgets 0x000000010387b088 _ZN7QWidget5eventEP6QEvent + 1096 30 QtWidgets 0x000000010392358d _ZN6QFrame5eventEP6QEvent + 45 31 QtWidgets 0x0000000103aacec9 _ZN17QAbstractItemView13viewportEventEP6QEvent + 1417 32 QtCore 0x0000000105310ceb _ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent + 155 33 QtWidgets 0x00000001038409d5 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 245 34 QtWidgets 0x0000000103841e11 _ZN12QApplication6notifyEP7QObjectP6QEvent + 497 35 Seamly2D 0x000000010284d702 _ZN12VApplication6notifyEP7QObjectP6QEvent + 18 36 QtCore 0x0000000105310a34 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212 37 QtWidgets 0x000000010386c2ab _ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 3467 38 QtWidgets 0x0000000103875100 _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 1120 39 QtWidgets 0x0000000103874f9d _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 765 40 QtWidgets 0x0000000103874f9d _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 765 41 QtWidgets 0x000000010386c5c5 _ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 4261 42 QtWidgets 0x0000000103875100 _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 1120 43 QtWidgets 0x0000000103874f9d _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 765 44 QtWidgets 0x0000000103874f9d _ZN14QWidgetPrivate22paintSiblingsRecursiveEP12QPaintDeviceRK5QListIP7QObjectEiRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 765 45 QtWidgets 0x000000010386c5c5 _ZN14QWidgetPrivate10drawWidgetEP12QPaintDeviceRK7QRegionRK6QPoint6QFlagsINS_14DrawWidgetFlagEEP8QPainterP21QWidgetRepaintManager + 4261 46 QtWidgets 0x000000010384df86 _ZN14QWidgetPrivate10scrollRectERK5QRectii + 9062 47 QtWidgets 0x000000010384c455 _ZN14QWidgetPrivate10scrollRectERK5QRectii + 2101 48 QtWidgets 0x000000010389ba54 _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 17748 49 QtWidgets 0x0000000103898a46 _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 5446 50 QtWidgets 0x00000001038409ea _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 266 51 QtWidgets 0x0000000103841e11 _ZN12QApplication6notifyEP7QObjectP6QEvent + 497 52 Seamly2D 0x000000010284d702 _ZN12VApplication6notifyEP7QObjectP6QEvent + 18 53 QtCore 0x0000000105310a34 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212 54 QtGui 0x000000010451e7f2 _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE + 306 55 QtGui 0x00000001044fa8f3 _ZN29QWindowSystemInterfacePrivate23handleWindowSystemEventIN22QWindowSystemInterface19SynchronousDeliveryEEEbPNS_17WindowSystemEventE + 115 56 QtGui 0x0000000104501f92 _ZN22QWindowSystemInterface17handleExposeEventINS_19SynchronousDeliveryEEEvP7QWindowRK7QRegion + 178 57 libqcocoa.dylib 0x000000010425f20c qt_plugin_instance + 101292 58 libqcocoa.dylib 0x0000000104267afb qt_plugin_instance + 136347 59 AppKit 0x00007ff80dfeae05 -[_NSBackingLayer display] + 462 60 AppKit 0x00007ff80df603ad -[_NSViewBackingLayer display] + 554 61 QuartzCore 0x00007ff812526a07 _ZN2CA5Layer17display_if_neededEPNS_11TransactionE + 873 62 QuartzCore 0x00007ff81267e2aa _ZN2CA7Context18commit_transactionEPN

(there’s more but can’t add due to character limit)

[Douglas]

@Karu

work on mac as well. i have faced this problem too. additionally now the app crashed

Thanks for the report(s). I really need to figure this issue with the Macs out. There’s something the MacOS doesn’t like. I suspect a bad or null pointer or possibly a font issue in the fx dialog.

I might have asked this before, but does the issue happen as soon as the fx button is pressed? Or after pressing Ok / closing the dialog?

[Karu]

@Douglas thanks. looking forward to the fix. any idea if there’s a way around the fx problem I shared. absolutely unable to draw patterns currently

[Grace]

I replied on your other post. I see that your computer hasn’t had its RAM cleared for a while now, and clearing the RAM helped to sort out a few issues with my customer , so I can only suggest that you try it.

[Karu]

restarted my laptop, it still crashing when i want to use fx

[Grace]

I’m so sorry. The other work-around would be to download the release around Aug 2021, for now. I’m not too sure which actual date of the release, but you will find the releases here: Releases · FashionFreedom/Seamly2D · GitHub

You will need to uninstall the current program and install the other one until you find exactly which is the latest working release.

Please will you let me know which one actually works, so that @Douglas can check what went wrong between it and the later releases?

Thank you

[Douglas]

@Grace

Please will you let me know which one actually works, so that @Douglas can check what went wrong between it and the later releases?

That’s what’s baffling me… I have checked the formula dialog against older versions of the source, and I don’t see anything different.? What is different is moving to Qt 5.15.2, different compiler ver, different workflow on Github.

The only thing I see is a conditional macos compile define to add certain Window flags to the dialog window. Theoretically it should be compiling correctly, as that condition is used all over the place for a mac build. I’m going to try and remove the condition, and just add the flags for all builds… like it is elsewhere like the Variables and History dialogs.

If I had a Mac, I could just run a build in debug mode and step through until the issue pops up. Most of the time you can look at the code at the breakpoint and class data and go Aha! BUT, of course that’s not an option.

[Karu]

so until i try with the older versions I can share that I used to have an older mac - until sept 2021 - valentine and seamly has worked beautifully on it.

In Sept 2021 I got a new laptop with M1 chip - might it be some incompatibility between the same old seamly with the new M1 chip?