loukash

I'm happy to report that the App Store version 1.7.1 now runs on Mountain Lion again. Thanks!

P.S. Reverting to AP v1.6.7 from Time Machine backup for now. P.P.S. I liked the new icon and welcome screen design…

Updated to v1.7 via Apple's App Store on Mac OS X 10.8.5 Mountain Lion. On launch AP crashes. The crash report is pretty short and obvious: Process: Affinity Photo [16074] Path: /Applications/Design/Affinity Photo.app/Contents/MacOS/Affinity Photo Identifier: com.seriflabs.affinityphoto Version: 1.7.0 (1.7.135) App Item ID: 824183456 App External ID: 829371620 Code Type: X86-64 (Native) Parent Process: launchd [191] User ID: 501 Date/Time: 2019-06-06 22:45:21.358 +0200 OS Version: Mac OS X 10.8.5 (12F2560) Report Version: 10 Interval Since Last Report: 34134161 sec Crashes Since Last Report: 16178 Per-App Crashes Since Last Report: 3 Anonymous UUID: 591BA059-F9FA-5879-5EAA-1D08D0A9C0F5 Crashed Thread: 0 Exception Type: EXC_BREAKPOINT (SIGTRAP) Exception Codes: 0x0000000000000002, 0x0000000000000000 Application Specific Information: dyld: launch, loading dependent libraries Dyld Error Message: Library not loaded: /System/Library/Frameworks/MapKit.framework/Versions/A/MapKit Referenced from: /Applications/Design/Affinity Photo.app/Contents/MacOS/Affinity Photo Reason: image not found Binary Images: 0x1088f1000 - 0x108996ff7 +com.seriflabs.affinityphoto (1.7.0 - 1.7.135) <1685DA61-BED8-398D-9D35-FBE6DAD75228> /Applications/Design/Affinity Photo.app/Contents/MacOS/Affinity Photo 0x1089e6000 - 0x108e9bff7 +liblibmetadata.dylib (1) <3504B77A-BCE8-3E30-88FC-92F165F371D9> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibmetadata.dylib 0x109367000 - 0x10941efff +liblibregex.dylib (1) <CE45E278-1A3C-3260-8F1A-4FBF8389C1D4> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibregex.dylib 0x1094b0000 - 0x1094b4ff7 +liblibhunspell.dylib (1) <69BD5FF3-0B3A-381E-A06C-2DE6E92F128F> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibhunspell.dylib 0x1094bc000 - 0x10975cfff +liblibicu.dylib (1) <DD2B3DF7-A4A6-3BDD-92FC-997AB92FB0A8> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibicu.dylib 0x1098ac000 - 0x10a7f1ff7 +liblibaffinity.dylib (1) <D2BD5822-1497-3863-A9FA-5024ACDB5F67> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibaffinity.dylib 0x10af7e000 - 0x10b092ff7 +libxmp.dylib (1) <39BB1A88-B8E4-3141-AA5D-897B61158CAD> /Applications/Design/Affinity Photo.app/Contents/Frameworks/libxmp.dylib 0x10b106000 - 0x10bc3eff7 +libpdfimport.dylib (1) <F694C1A4-811E-3CC9-A28D-FAD70DDA84E9> /Applications/Design/Affinity Photo.app/Contents/Frameworks/libpdfimport.dylib 0x10c17a000 - 0x10c28eff7 +liblibgeometry.dylib (1) <98584F38-EDD1-3055-8A26-950C2B4E43A2> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibgeometry.dylib 0x10c301000 - 0x10c329fff +liblibgl.dylib (1) <4AA075C9-27F2-33CC-A68D-9A8D8AABB95B> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibgl.dylib 0x10c343000 - 0x10c39bff7 +libliblittlecms.dylib (1) <23C734B0-9A21-3FAB-AD7F-D1245870DB52> /Applications/Design/Affinity Photo.app/Contents/Frameworks/libliblittlecms.dylib 0x10c3ba000 - 0x125b7cfff +liblibpersona.dylib (1) <7C35E415-7C6D-3458-9BC5-CE6A9F517B7C> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibpersona.dylib 0x130f36000 - 0x1311acfff +liblibkernel.dylib (1) <820DC9F5-4916-3B42-A104-A7C032E6DD14> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibkernel.dylib 0x1312a1000 - 0x1328e6ff7 +liblibraster.dylib (1) <F1527E66-8D49-3F53-BAF9-657205AA0228> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibraster.dylib 0x13331c000 - 0x136ba0ff7 +liblibrenderer.dylib (1) <D2F68FA3-54A4-307B-9DD6-6A570F519C0D> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibrenderer.dylib 0x138ccc000 - 0x138f31ff7 +liblibstory.dylib (1) <4B253501-59D5-37CB-A766-B46DA15A9769> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibstory.dylib 0x139072000 - 0x139082ff7 +liblibxml.dylib (1) <CC305E90-853D-33D7-8308-F9386F7C671B> /Applications/Design/Affinity Photo.app/Contents/Frameworks/liblibxml.dylib 0x139098000 - 0x13ae72fff +com.seriflabs.libcocoaui (1.0 - 1) <497CDB24-E910-3E37-AD6A-1371D74EB2BF> /Applications/Design/Affinity Photo.app/Contents/Frameworks/libcocoaui.framework/Versions/A/libcocoaui 0x7fff684f1000 - 0x7fff6852593f dyld (210.2.3) <6900F2BA-DB48-3B78-B668-58FC0CF6BCB8> /usr/lib/dyld Model: MacBookPro9,1, BootROM 224.0.0, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.1f175 Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 384 MB Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.17) Bluetooth: Version 6.1.7f5 15859, 3 service, 13 devices, 4 incoming serial ports Network Service: Wi-Fi, AirPort, en1 Serial ATA Device: APPLE HDD TOSHIBA MK7559GSXF, 750.16 GB Serial ATA Device: HL-DT-ST DVDRW GS41N USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1a100000 / 2 USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8509, 0x1a110000 / 3 USB Device: hub_device, 0x8087 (Intel Corporation), 0x0024, 0x1d100000 / 2 USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0x1d180000 / 3 USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x1d182000 / 6 USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0253, 0x1d183000 / 5 USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x1d181000 / 4 USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x821d, 0x1d181300 / 9 If AP 1.7 should be compatible with Mountain Lion, then it shouldn't be dependable on the MapKit.framework, of course… Affinity Designer 1.7 works fine as far as I can tell, by the way.

This is good news. Just yesterday I thought I'd give AP another try within my usual image editing workflow, but got completely stuck at something as trivial as cropping. Seriously: The current cropping concept is one of most counterintuitive workflows I've ever encountered in any professional Mac software. (Disclosure: Frankly, as a Mac user since 30 years I have absolutely no idea how counterintuitive Windows software can be…)

From what I can say so far, it's an OS issue: • No offer to be seen on Mac OS X 10.8.5. Mountain Lion. • Once I have booted the Mac from a macOS Sierra partition, the offer was there right away. So the culprit is possibly WebKit? WebKit on Mountain Lion is pretty much broken nowadays, due to lack of TLS 1.2 support.

The lack of those vector effect features is the main reason why I still end up doing all work in Illustrator (CS5, for the record), usually after wasting hours of my time attempting to figure out how to achieve this in AD. :/

Thanks for confirming that it's actually supposed to work. At first I thought it's not even possible to rename them. That is: using the Control key actually doesn't work for me at all. What does work every time is tapping with two fingers on the MacBook trackpad to simulate a right click. Yeah. Not only that, actually I want to be able to save the complete Batch Output section: the destination, the format, the format settings, the applied macros. The basic idea is all there. Why stop on half of the way? My experience with Affinity Photo so far is that every time I attempt to replicate anything from my usual Photoshop workflows (I started with PS 2.5 over 20 years ago, working with CS5.5 these days), I get stuck about half the way through, waste about an hour, give up, and return to Photoshop to have it all done within a few minutes… :/

D'oh, I am, obviously: The Export Selected check box in the palette must be enabled to edit an existing slice. Not very intuitive, but the "non-editable" problem solved as it seems… Still, linked slices not being automatically moved with artboards smells like a bug to me anyway.

Well, not always. Probably a bug: 1) I have created several artboards in Designer, then in Photo I added various pixel layers, created linked slices and exported. 2) A couple of weeks later, I added another artboard in Designer while rearranging the older artboards. Again added more pixel layers in Photo. In the Export Persona though, the slices remained at their original absolute positions, either on different artboards or completely outside. When I select them in the Slices palette, they are not editable. I can only create new ones. Or am I missing something?

Good news, thanks!

No, I was asking about the upcoming versions 1.5 of Photo and Designer as discussed in this thread. (My personal reason: On the one hand more and more updated apps out there are dropping support for 10.8.5 in general which is a bit unfortunate, because on the other hand more and more audio hardware manufacturers are dropping driver support for current versions of OS X, making me stuck with 10.8.5 and a bunch of at their time quite expensive but still perfectly working audio interfaces…) ~~~ But… à propos Publisher: any news on the release date…? :)

How about system requirements? Will OS X 10.8.5 still be supported?

In the meantime I've noticed this is the same issue as also posted here: https://forum.affinity.serif.com/index.php?/topic/15915-layers-problem-in-affinity-designer-after-upgrade/

In the meantime I've figured out a temporary workaround: Nested layers can be expanded via context menu. Once expanded, the expand triangle becomes visible. Eventually if all layers/artboards are collapsed though, the triangles will disappear again.

Nested layers and artboards with layers cannot be opened and viewed in the Layers palette. There is the circle where the opening triangle should be, but clicking it only selects the layer/artboard. The triangle is apparently still there, hidden and unclickable under the "Enable/Disable Layer" check mark at the right edge of the palette. If there are two or more artboards, no layers are visible at all, only the artboards, again with the empty circle and the barely visible triangles under the check mark. The bug is present both in AD and AP 1.4 on OS X 10.8.5. (No newer OS X installed and no plans to upgrade anytime soon.)