Walda57

Moin an alle, falls nicht schon überholt: im Publisher 2 drückt man, wenn man im Textrahmen ist, ESC, dann kann man mit V sofort das Verschieben-Werkzeug aktivieren.

It worked! Many thanks. Will this happen again or is the bug fixed now? I closed it and opened again, it worked. So, by the way, you're doing a great job at Serif with the Affinity suite! Keep on!

Uploaded the crash report to your Dropbox. Thanks in advance!

Apple says: EXC_CRASH (SIGABRT) EXC_CRASH (SIGABRT) indicates the process terminated because it received the SIGABRT signal. Typically, this signal is sent because a function in the process called abort(), such as when an app encounters an uncaught Objective-C or C++ language exception. Addressing language exception crashes explains how to handle uncaught language exceptions in more detail. If there isn’t a Last Exception Backtrace indicating a langauge exception triggered the crash, look at the crashed thread’s backtrace to determine if code in the process called abort(). When an app extension takes too much time to initialize, the operating system sends a SIGABRT to the app extension process. These crashes include an Exception Subtype field with the value LAUNCH_HANG. Because extensions don’t have a main function, any time spent initializing occurs within static constructors and load() methods present in your extension and dependent libraries. Although the exception information is different in a watchdog termination, investigate the LAUNCH_HANG with the same techniques discussed in Addressing watchdog terminations.

Sorry, saw the post just now. If I start from applications or Launchpad with the Control-key held, I can clear some settings (what I did) but the crash occurs, nevertheless. Shall I submit the new crash report, too? The crash is again SIGABRT.

I face a similar bug: starting Designer 2 on my MacBook pro (2018, Ventura 13.1, i5) I see the starting graphics (of version 2.0.3), then get an "unexpected error" message. In the crash report I find a "EXC_CRASH (SIGABRT)" notice. ADe2 works well on my macs and on iPad. Also do Publisher and Photo on all machines. Any idea how to fix?

Hope, a pdf works too? Otherwise, see the txt-file. Affinity Designer 2-2023-01-18-092544.pdf Affinity Designer 2-2023-01-18-092544.txt

I opened the crash report on ADe2. Who will be the recipient? I'm not as skilled with to read them as needed.

Hi everybody, I used Affinity 1 with great fun and Version 2 is also running well. There are no problems on my different machines (Mac, MacBook pro and iPad). They all work, only Designer 2 on my MacBook pro (2018, Ventura 13.1, i5) starts (you can see the graphics of version 2.0.3) but then stops and the message appears that an unexpected error occurred. Photo and Publisher start without any problem. Even uninstalling all files and install them new didn't help. Also to download the file again and install it didn't help. I found no problems in the preferences (safety etc.). Is there any idea what the reason could be?

Hi everybody, Is there any possibility to set different colours to a set of auxiliary lines? It would be very helpful to differentiate between different sets of lines. If not available: Serif: is it planned to have this possibility and if, when? Second part: the auxiliary lines for columns can be defined in a broad range. But if I want to define different spacing between vertical and horizontal lines, to define the fields for labels exactly, e.g., there´s only the possibility to define one space. Any solution available? Or, as before: Serif: is it planned to have this possibility and if, when?

Many thanks to both, Babelfisch and GarryP: it works. I work a lot with QuarkXpress, where the metadata are set differently and didn't find them here. So thanks again!

Creating larger documents needs to place a page number on each page. Often, especially in technical documentations, it's also needed to insert the total number of pages of the document, as well (page 5 of 50, e.g.). For the first you can insert a field with "page number", that works well. But in the latter case there's no field given. The other fields "next / previous frame page number do not deliver the correct result. How to do this? You can wait until the end and insert the real number on the master pages. But that's not the way. Any addition of a page leads to a lot of changes needed. So, who can give advice how to automate this, too? If not given: Affinity, when will you be able to offer this feature?