GaryLearnTech

You certainly can. I have my copies on both my personal iMac at home and my office iMac at work. You've mentioned the version of macOS that's installed on your problem iMac, but you've not said a word about the model. Perhaps the problem stems from not meeting the hardware requirements? Take a look here: https://affinity.serif.com/en-gb/photo/full-feature-list/ https://affinity.serif.com/en-gb/designer/full-feature-list/ If you don't know your iMac's specs off the top of your head, go to the  menu and select About This Mac - that should clarify most of the points mentioned as the requirements…

I wonder if this might not involve a system level override being provided/applied by macOS itself?'  > System Preferences > Keyboard > Text

The ability - yes. Templates baked-in to make it easy - sorry, no.

Maybe I'm missing something here, but can you not simple multiply the floating stop values by 100? That will map your existing range of 0 to 1 to the full Affinity percentage range? For example Stop 0.0000 0.00% Stop 0.0071 0.71% Stop 0.0286 2.86% Stop 0.0857 8.57% Stop 0.1429 14.29% Stop 0.2857 28.57% Stop 0.4282 42.82% Stop 0.5714 57.14% Stop 0.7143 71.43% Stop 0.8571 85.71% Stop 1.0000 100.00% I'd suspect that you want/need to round off your percentage decimals, but I think it should otherwise sort your issue…

Hi @curtsheller - this is no more than a stab in the dark (but from a guy who has been doing support and trouble-shooting of one form or another for longer than some of the participants around here have been out of nappies (or, depending upon where you hail from, diapers)). The path indicated in your screenshot looks as if it could be on an external drive. I've seen a number of reports in recent years of issues - in general - with some apps when saving to external drives. Could be to do with permissions on the drives, especially if they're network rather than USB drives? Dunno, but they're out there. What happens if you simply export to, say, your Desktop in the first instance? If that doesn't work, is your source Publisher document on your boot drive or is it also on the suspected external drive? If not, can you make a copy and repeat the test?

@Petar Petrenko the ctrl-t shortcut I was talking about for Macs comes from the system level, ie it's a core part of the operating system. I seem to recall it's permanently turned on - I don't think there's anywhere it needs to be configured for it to work. Then, for any app that have used the appropriate developer libraries, you find it simply works without having to do anything special. I'm afraid I don't know if there's an equivalent option in Windows, sorry. I suspect maybe not. My vague memory is that ctrl-t is an ancient short-cut from either Unix operating systems (which macOS was originally built on) or either of the popular Unix text editors: vi or EMACS.

For colleagues using Macs, ctrl-t should work to exchange two adjacent characters - as demonstrated by @v_kyr. I believe this applies by default to apps that use certain core developer libraries, rather than implementing their own text-handling routines (yes, I'm looking at you, Microsoft Office ). Fortunately, this shortcut does work in Publisher (and will almost certainly work in Designer and Photo too). Sorry, @Petar Petrenko, I know your signature indicates you're a Windows user - I don't know if there's an equivalent that you can already use with out any further configuration.

You wouldn't by any chance have a firewall running, in which a rule might have been set that's blocking the content from coming down?

I took a quick look at that first, but reckoned you couldn't do exactly what the OP wanted. It is certainly a powerful feature though, that could be better known.

Glad to help. Watch out for the occasional promo where the price is dropped. You can see the price history here for the Mac App Store version. Since you can't predict jobs like this, it's worth having in your toolbox even if only for once or twice a year - and if you can pick it up cheap…

Another approach, since @dedolightamericas is on a Mac, would be to use a utility such Better Rename to handle the renaming. You can get it from the Mac App Store or direct from the publisher (where a free trial is available). You have the choice of many different rule types available and can see a live preview of the results you'd get when you finally tell it to proceed. It looks to me as if you'll have to break this down into batches due to slight variations in the naming, such as single digits versus double digits being adjusted. This screenshot shows the first step I'd use, based on your initial sample. Read the screenshot from left to right: The second step would use the same command to exchange the first two characters to put the numeral first, followed by the hyphen. These steps can be built up and run as a single batch, so adding the second step under the first one in the left hand column would look like this, with the preview of the final renaming in the right hand column: When it runs, it's very fast. I used this about 18 months ago to work through an old set of clip-art CD's that I had copied onto an external USB 3 disk. As with this, I had had to break the job down into batches, but it got there. Sets of steps, such as shown above, can be saved as presets and easily recalled in the future, rather than rebuilding from scratch.

I have just tested this with exporting pages (not spreads, though I don't think that would make the slightest difference) first to PNG's and then to JPG's. And in each case, I got one image file per page - exactly what you've asked about. I honestly don't think it could have worked any other way - neither PNG nor JPG are multi-page formats. Your PDF export doesn't work that way right now - but it might be possible to find an external utility to split your multi-page PDF files into single-page files. In fact, I'm on a Mac and it's the work of just a couple of minutes to put together an Automator workflow that specifically does this. The resulting single-step workflow (a simple standalone desktop utility) just requires you to drag and drop your PDF onto it and it will produce the individual page files. One caveat… There seems to be a bug - at least on my machine - where it fails to remember the Save Output target (shown above as a folder called TEMP). In each of several tests, the split files ended up on my Desktop and not where I'd asked them to go. Not too big a deal with an 8-page document, but could be inconvenient with 100 pages. Certainly not insurmountable, but definitely inelegant. If I was going to be using this myself, this might be a good enough reason to experiment with a little AppleScript to do the same job to avoid this bug. Dunno how easy this would be if you're a Windows user, but I'm sure it could be done one way or another.

Hi @LibreTraining This same preference panel appears in each of the Mac versions of Designer, Photo and Publisher. My versions are each simply v1.7.1, with Designer and Photo coming from Apple's Mac App Store and Publisher coming from Serif's own store. No beta versions. I don't recall the exact list of options that would have been available when this thread originally ran just under two years ago but if it wasn't the exact same as now, it wasn't far off it. In other words, not much has changed for this on the Mac version. A more detailed version of this exists - at least it does on the Mac - if you hold down ctrl-option (aka ctrl-alt) when the app is launched. I've seen this mentioned here several times over the years. I would imagine you'd have something similar on your Windows version - production or beta. This screenshot obviously shows the options for Designer. Photo has a few more options and Publisher one more option than Photo.

Looking at the selection of data that can be reset, I'd guess that each Affinity application builds its own caches and uses that data to speed up day-to-day operations. Reseting, say, Fonts would then clear the relevant cached data and cause it to be rebuilt afresh. In cases where the cached data has somehow become corrupted and has begun to cause problems, discarding the cached data and recreating it would resolve some of those problems. @thomaso in the case you describe, that might be the equivalent of a "micro reset" - causing the cached data for an individual font to be first cleared and then recreated. But that's just a guess. Anyways, glad my old comment was able to help @Father ODD Creations!

Oh, that's a good one. Thanks @Old Bruce, I'd not come across that functionality before.