AlanH

Thanks all for your suggestions: First of all, today both PCs are behaving with the file that caused an immediate crash on font select. I have no idea why. Machines' update history shows no quality (KB) updates since 14 Dec, i.e. before I last posted here. @carl123 OK, I have switched that to 'off' on both machines, but as noted above, the file is now working OK on both platforms. @blackstone I suspect that would have been the case on mine if the 'bad' file had not started behaving. @SrPx Both my installations have SSDs as their system drives with OS and all fonts on board. Graphics drivers are kept up to date, and the two platforms have different GPU cards (NVIDIA and AMD). I will run SFC and DISM when I have time. For the time being, I will monitor the situation for font crashes. I have no idea why the machines have both started behaving....

I think it must relate to the .NET configuration of particular computers...

And the same with my Win11 machine. See examples of both in attached video... PUB2FONTSELCRASH.mp4

This had been fixed by the later versions of Suite v1, but reappeared yesterday on my Win 10 machine in Publisher v2.0.3 (but I assume Designer/Photo will do the same.) The v1 update removal list is no longer relevant, so what do we do now for v2 on Win 10? The only KB updates I have installed at present are: 5012170, 4598481,4593175,4586864,4577266,5003791,5000736,4562830 Suite apps are not usable at the moment due to this! Cheers, Alan

OK thanks, Callum - I have raised it as a feature request. Alan

I raised this as a question, but as it seems the function is not available, I propose it here as a new function: Request Please allow configurable filenames for image file exports, ideally using wildcards. At a minimum, it would be useful to have files named <Publisher Filename>_<Section (name or number)>_<In-section page number> instead of just <Publisher Filename>_<Global page number> as at present. Rationale (one example) I use Affinity Publisher to create graphic overlay screens for use with my video editor software, Vegas Pro. After any change to the Publisher file, I export all its pages as PNG files, over-writing all previously exported files. As the PNG files are explicitly referenced in Vegas, they update automatically on the project timeline. This is a particularly convenient solution for last-minute global changes to text, fonts, logos etc. For ease of use, I group sets of similar pages using Publisher's "Sections" function, with meaningful section names (e.g. TITLES, CREDITS, LOGOS, SUBTITLES etc.), restarting page numbering for each section. As it stands, Publisher simply exports all images with filenames <Publisher Filename>_<global page number>.PNG Having PNG (or other graphic) files export with names constructed from the Section name and in-section page numbers would enable me to add pages to individual sections without disturbing existing file names (which, as mentioned above, are hard-referenced in the video editor.)

It would be useful for work on large documents if the page thumbnails could be (optionally?) labelled with Section Name and Section Page No. rather than the global page number. Section numbers (e.g. Section3, Page 5) would be acceptable if the section names were too long to fit.

I have just found this topic while preparing to make the same suggestion. Dark Mode is much more relaxing to work in, so would it not be possible to replace that barely-discernable grey border on the active thumbnail with, say, a bright yellow one? Like Eusebius, I also struggle to identify active pages in documents with near-identical pages.

Question Can Publisher export PNG (or other graphic) files with names constructed from the Section name and in-section page numbers? Background I'm using Affinity Publisher on PC to create graphic overlay screens for use with my video editor software, Vegas Pro. After any change to the Publisher file, I export all its pages as PNG files, over-writing all previously exported files. As the PNG files are explicitly referenced in Vegas, they update automatically on the project timeline. This is a particularly convenient solution for last-minute global changes to text, fonts, logos etc. For ease of use, I group sets of similar pages using Publisher's "Sections" function, with meaningful section names (e.g. TITLES, CREDITS, LOGOS, SUBTITLES etc.), restarting page numbering for each section. As it stands, Publisher simply exports all images with filenames <Publisher Filename>_<global page number>.PNG Having PNG (or other graphic) files export with names constructed from the Section name and in-section page numbers would enable me to add pages to individual sections without disturbing existing file names (which, as mentioned above, are hard-referenced in the video editor.) If there's a way to do this, I've not found it yet. And yes, I know I could manage each Section as a separate Publisher document, but that defeats the object of having a common workspace for graphical assets, and means more project files to manage. I could also do this with Designer (and I used to), but as page counts grew to over 100, Publisher with its Master pages seems the much better option. Regards, Alan

Thanks, Callum!

Affinity Publisher 1.10.4.1198 on Windows 11 (for my sins)... Select a plain coloured rectangle in a Master page in Publisher, then select Photo persona. Immediate crash when Perlin Noise Filter selected. Standalone Photo (same version/platform) does not crash with the same function. Cheers, Alan

After years of sloppy practice, I have finally got into the habit of naming my drawing element and group layers as I create them. When I Ctrl-G to create a new group, would it be possible to have the newly-created group label open with the cursor ready to give it a name? The return button could simply be hit without typing anything if no label was required. This might encourage routine group naming. Sorry if it turns out this option already exists!

@Jon PThanks, I will do that pro tem. Have a good Christmas! (finally figured how to do that "mention" thing!)

Something springs to mind - this problem seems to have arisen since I purchased the Christi's Comix Toolbox brushes set and installed them across the Affinity suite. Any possible connection?

Hi @Jon P - Thanks for the suggestions. I have had a go at them this evening: a) I downloaded the beta version and using the same document, I could not get it to lock up while scrolling fonts - admittedly exercising it only for a few minutes, but that's much longer than the current active version. In case my computer had suddenly got better, I went back and re-checked the current version, and it still locked up in about half a dozen font select scrolls. That may be a good sign, but why would the Beta behave differently? b) Re. the Crash Reports, the only place with an Affinity folder is Roaming, i.e. C:\Users\Alan\AppData\Roaming\Affinity\Publisher\1.0\CrashReports but the \reports folder under that is empty. I think Publisher is locking so hard that it cannot actually 'crash' i.e. close down, so no crash report is being written when I finally get fed up with waiting (up to several minutes) and terminate it via Task manager. c) Re. fonts, I have limited experience with fonts beyond installing and removing them via the c:\windows\fonts folder. Two observations: 1. When I select them all and try to zip them, 7-zip tells me there are duplicate file names and refuses to work. I read somewhere on the web that the 'real' font files are in c:\Windows\SxS\ and when I search the massive list of folders under that for *.ttf, I do see most fonts appearing twice and some three or four times. It's a mystery to me, I'm afraid. 2. I have tried to remove all unnecessary fonts as part of this exercise, but find some will not respond to the Remove option, and stay in greyed-out form. So the Beta seems to be better, but maybe my current font situation is not 'textbook' and needs some rationalising, but that's outside my skill-set at the moment! Regards, Alan