-
Posts
19 -
Joined
-
Last visited
-
I've been trying to download the free extras pack without success. I am an existing customer, and have tried using the password I use for this forum to claim the pack. That doesn't work - 'sign in details are incorrect comes up'. I purchased originally via the Apple store. Would welcome some advice!
-
Alfred reacted to a post in a topic: why is affinity opening a second icon in the dock?
-
Alfred reacted to a post in a topic: why is affinity opening a second icon in the dock?
-
...yes, right clicking shows Affinity 1.5.2, and opening images from within the app itself works fine, showing just the one icon in the dock. There is a 2nd dialogue box that follows the 'AP is already open' box. That reads: 'Affinity Photo quit unexpectedly. Click reopen to open the application again. Click report to see more detailed information and send a report to Apple.' (There's also an option to 'Ignore'.) The reopen option just takes you back to 'AP is already open', and another crash. The 'Problem Report for Affinity Photo' is extremely long, but the intro summary says: Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000008 Exception Note: EXC-CORPSE_NOTIFY My MBP is a mid-2015 and works perfectly in every other respect.
-
I've noticed recently that if I have Affinity Photo active in the dock, then choose an image file and right click 'open with' Affinity Photo, a second AP icon appears in the dock - both shown as active. A dialogue box then tells me that "Affinity Photo is already open'. I click OK, and the app crashes. I'm using 1.5.2, running on 10.11.6. What's happening here?
-
I've been extremely impressed with Affinity Photo for some time now, and so far I am mostly very pleased with 1.5.1 However, when I tested the macros that came in the bonus pack, my 2015 MacBook Pro Retina got very worked up - the fans immediately came full on, which it is a first. I have never even heard them before, even with Final Cut. The MBP is a 2.5GHx Intel Core i7, with 16GB RAM. Shouldn't it cope easily with your macros? Or is there a bug somewhere?