Martin S Taylor

The Performance Pane looks like this. Is there any more I need to do? Martin

Turned off Metal, but both Publisher and Designer had crashed when I came to my computer this morning. Martin

As promised, I'm reporting that Affinity Publisher crashed again today. I wasn't even there! I left the machine to go to sleep on its own, and when I woke it up this evening there was the crash report. I've now turned off Metal, as MikeTO recommended and we'll see what happens. If it still crashes I'll try downgrading to 2.4.0 Martin

I do have Metal on, so perhaps that's the problem. I doubt that it's our settings of Affinity, as these crashes affect all the Affinity programs - Photo, Designer and Publisher. I also wondered if some background programs I run could be causing the problem, so I've disabled them. If this makes no difference I'll turn off Metal and see how that goes. I'll report back, in either case. Martin

(Following the reply from Dan C, I'm starting a new thread, as requested.) As per the title, all three Affinity products (Photo, Designer and Publisher) crash at random times, usually when I'm not using them, and often when these apps have no windows open. I would say on average I get about one crash a day. As Dan C recommended, I reset Affinity back to default settings, but the problems are persisting. Latest crash report attached. Martin MacBook Pro M1 Max. MacOS 14.4.1 Affinity versions 2.4.2 Affinity Publisher2 crash report.txt

Thanks. I've done what you suggest, and we'll see what happens. Martin

As per the title, all three Affinity products (Photo, Designer and Publisher) all crash at random times, usually when I'm not using them, and often when these apps have no windows open. I would say on average I get about one crash a day. Crash report attached. Martin MacBook Pro M1 Max. MacOS 14.4.1 Affinity versions 2.4.2 Affinity Crash Report.txt

My vote for restoring separated mode, too. Please can we have it back? MST

Is there any reason why Designer won't allow you to add a border to a text frame? It seems to be a curious omission. Martin

Aha! Thank you. It was the option "Superscript ordinals as they are typed" which confused me. It seems that this option forces faux-superscripts in appropriate places. Thus when I type "18th", it uses the faux-superscript 'th'. But If I select the option under typography, I get weird results because Garamond has a 'proper' superscript 't' but not a superscript 'h'. Martin

I'm having trouble getting Ordinals to work properly. In my chosen font (Garamond Pro) , if I type a phrase like "19th Century", the t of '19th' appears as superscript, but the h doesn't. In Times New Roman the superscript goes very weird, as you can see from the screenshot. For what it's worth, "Superscript ordinals as they are typed" (in Settings) is switched off, but "Ordinals" (in the Character Palette), is on. Martin S Taylor Sonoma 14.0; Publisher 2.2.0

My point exactly. Better still, if Next Style is set to '[Same Style]', then don't strip the character style or local attributes. But if Next Style is set to the name of the paragraph style itself (not currently an option) then do strip them. MST

That's the problem. The style I'm working in is called 'Listings'. If I could set Next Style to be 'Listings', this would probably work, but I can't do that – 'Listings' isn't there as an option. All I can choose is '[Same Style]', and this doesn't strip out local formatting, as I've explained. MST

Yes, you're right and your workaround is good. I'm just a little surprised there isn't a way to start the new paragraph and automatically begin with a fresh text style, as it were, with no local formatting. MST

MacOS 13.2.1 and Publisher 1.10.6 Martin

I have a Text Style (called 'Listings') set up exactly how I want it. The text is in Garamond Regular (ie. not italic). However, I need the last few words of each paragraph to appear in italics. Easy to do, either with a Character Style or a local Italic override. But now I hit <Return> to start a new paragraph and the text continues to appear in italics. I'd like all that local italicising to be cancelled, so that the new paragraph begins, automatically, with the text style 'Listings', exactly as I've defined it – without italics. It's easy enough to cancel the italics manually. Or there's a stupid workaround, where I can define two identical text styles, 'Listings' and 'Listings 2', each of which is followed by the other. But this is a bit daft. Am I missing something here? Is there no way to clear local formatting automatically when I start a new paragraph in the same Paragraph Style? Martin

Don't feed the troll. I'm off this thread.

Seems straightforward enough to me: if you buy in Jersey, the price is £89.99; if you buy in mainland UK, the price is £74.99 + VAT. Serif can charge what they like in different countries. If you prefer your extra £15 to go to Serif, buy it in Jersey; if you prefer the £15 to go to His Majesty's Revenue and Customs, buy in the mainland. Martin

It is baffling that Affinity are letting this drag on so long without resolution, or even comment. If it's Affinity's fault they should fix it. If it's Apple's fault they should keep pestering Apple until Apple fix it. Martin

Certainly you need a driver, but I'm pretty sure there's a driver for Canon printers built into the MacOS. I never installed anything from Canon onto my Mac – I just plugged in the printer-scanner and it works (except with Affinity, which is why we're here). You certainly don't need Canon's tools for scanning – Apple's work just as well, though you can use Canon's if you prefer them. I don't understand what you mean here. MST

Better still, use Apple's "Image Capture", which comes as standard with all Mac software. Martin

I'm getting the same problems with my Canon TS8350 under Monterey (MacOS 12.0.1) Martin

Turning hardware acceleration off makes no difference. I get a similar result to Wilfred Hildonen, but only scanning in Black and White at 200dpi. Other resolutions, and colour scanning are fine. However, it won't scan at all if I set the scan to 'Text': "Scanner reported an error An error occurred during scanning." No problems using Image Capture. Martin

I don't know if this is the same bug, but scanning at 200dpi doesn't work – or rather, it produces weird results which other scanning programs don't produce. See the attached file. Martin Scanning bug.afphoto

For some reason they used the control key for this in Affinity Photo. The option key works as you described. Yes, it does. But one of the huge strengths of Macintosh has always been consistency between applications. For example, in 1980, to Quit a program sometimes it was Quit, sometimes it was Exit, or Stop, or Leave, or QQuit.... Apple put an end to that by saying it had to be 'Quit'. Similarly, all programs use Cmnd-X for Cut, Cmnd-V for Paste, etc. This consistency is worth maintaining, and I, too, would prefer it if Affinity marquees used the same keys as every other Mac program, sc. hold Shift to add to a marquee, Command to subtract from it. MST