Rabari

Running headers a la ID would really be nice. I do anthologies with different writers writing on the same subject, but with different headings. A running header makes it easy for the reader to jump around in the book, or to quickly search it without resorting to the TOC. The correct way to insert running headers is not to divide up your book into sections, but to define running headers on the Master Page, which simply are fields that pick up a style, for instance, "Heading 1” and ”Writer Name”, any time they are used in the layout, and with the possibility to insert desired punctuation in between. The end result, with another Style formatting the running header itself, looks like (I usually put them on the upper part of the page): Rabbe Sandelin – On the subject of Running Headers and a few pages foward Sabbe Randelin – Why We Need Running Headers (and Footnotes)

Opening and viewing the Publisher file in Photo, and using the Channels window actually works! Could we please get a Channels window in Publisher?

Limited search as suggested above, is a must.

Beta 1.10.2.1167 opened the file without problems.

When opening a certain file from 2019 Affinity Publisher (latest non-beta version 1.10.1 ) crashes. A terminal window pops up with attached information. The file is just a few pages with 3-4 linked jpeg-files, and nothing critical I can't recreate in an afternoon. But it would be nice to just open it for editing.

Sorry, missed your question. Hard to replicate, just when you think the problem is somehow solved - it crops up again. I'll attach a crash report next time. If I remember correctly the system font SF-[something] is often mentioned…

When I wake my Mac mini (2018 - 11.5.1) from sleep lasting more than a few hours, Publisher has often quit. I found this in the terminal: /Applications/Affinity\ Publisher.app/Contents/MacOS/Affinity\ Publisher ; exit; 2021-08-13 09:10:24.961 Affinity Publisher[67004:1082063] apply_selection_policy_once: prefer use of removable GPUs (via com.seriflabs.affinitypublisher:GPUSelectionPolicy->preferRemovable) 2021-08-13 09:10:26.069 Affinity Publisher[67004:1082063] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:]. 2021-08-13 09:10:26.069 Affinity Publisher[67004:1082063] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug. 2021-08-13 09:10:26.251 Affinity Publisher[67004:1082063] Duplicate menu item: orderFrontCharacterPalette: 2021-08-13 09:10:26.252 Affinity Publisher[67004:1082063] Duplicate menu item: saveDefaults:

Ok, I misread that to keeping a key down when opening the app by clicking the app icon. Doing that with option/alt did however reset something, At least the licence info and the initial starting window (which I usually dismiss with "Don't show this") popped up anew.

Interesting: When I chose "Customize Toolbar" the toolbar suddenly slided in from "above" and "left" of my second monitor. So it WAS there, just off-screen. The solution was to toggle the resolution of the second monitor - this moved the toolbar to my main monitor. Problem solved.

No amount of resetting the app (option key on a Mac), or clearing defaults helps. I downloaded the app from my account and installed it again, but to no avail.

I have the same problem after my update to 1.9.3. Regardless of how many times i uncheck/check "Show Toolbar" in the View menu, the toolbardoes not show up. Same goes for the context toolbar. I use Studio in separated mode, and earlier the toolbar has sometimes been lurking under the massive amount of tool panels on my second monitor - but not this time. The toolbar is truly nowhere to be seen. And resetting Studio did not help.

I do mainly page layout and photo editing/restoration, both at my "real" work place, and for my own small company during evenings and weekends. For my own little company even a monthly InDesign + Photoshop subscription would not make economical sense, as work assignments come and go very unevenly and are not especially higly paid, as I mainly work for non-profits and private persons. Just like many others, I was using the last non-subscription version of CS for as long as it was technically possible. So I was very happy when Photo came along, and when more was promised. The complete conversion to Affinity did not happen overnight. I started with Photo and Designer. When Publisher came along at about the same time Apple released Mac OS versions that would not run 32-bit InDesign anymore, the transition became complete. So far, there have been some hiccups and problems, mainly with the early Publisher versions, and mainly because of slightly different way of app ”concepts". User unrecoverable file corruption. I've stated this in many forum posts: the save files have to be completely rock solid, 100 %, no exceptions. Loosing a few minutes of work because of a crash is nothing, but loosing even a days work (my backups don't run continously, and frequent backups can also become unrecoverable) starts to hurt business reputations. Fortunately Affinitys support has, as far as I've seen, always managed to get corrupted files back into some servicable state. I had one of these cases also, and it was not funny, with customers breathing down my neck. crashes during pdf export (turned out to be greyscale graphic files which for some reason were assigned RGB profiles in Photo) color management inconsistencies: a document set up as "greyscale" exported as RGB. Didn't know I was supposed to set up CMYK documents, to output clean K documents But generally I am very happy, especially with the 1.9 versions of Publisher, which feel more solid. I'm however missing a few things, before I can get rid of my Mojave startup disk with ID CS6: Import of, and support for footnotes Tables that can be inserted into text frames, or at least tables that can span several pages (just like text frames)

Ok, thanks! Strange combination indeed, for files coming out of Affinity Photo Sorry, untouched photos. Why do people scan B/W photos in RGB? Could problematic files like these be flagged in Pre-flight, perhaps?

Ok, uploaded now. Maybe a contributing factor to problems: this is a file which has been "re-used" a couple of years, where I open up the file from last year, empty out old stuff to put in the new. Could there be some old cruft left? If I remember correctly this project has had similar problems earlier, but they resolved with a new version of the app. Might even be that the original file was made with one of the pre-release betas…

Having big problems exporting to pdf; the dreaded and very unhelpful "An error occurred while exporting to:…” Version 1.8.6. MacOS 10.15.7 File is normal A3, 20 pages, jpegs, tiffs, pngs – nothing unusual. Tried normal troubleshooting: restarting, giving more memory, software rendering, looking for bad links, strange graphics, old broken fonts, etc but no luck. No pdf preset works, built-in or own. Strange anomaly: Export window never finishes calculating Estimated File Size. Beta version opens file, but crashes on trying to choose any pdf export preset. Now a deadline is looming. Cannot afford to loose this gig.