Like, would like more if…

@Affinity Info Bot Have been experiencing exploring this problem and tried opening in Beta 2.6.4.3557 and it appears to have made no difference at all. The issue is any artwork that has a presence on the left hand page and carries over to right hand page will not show on the right hand page when output as single page PDFs. Issue is not with spreads. The issue occurs with all native Affinity files and EPS files, works properly with SVG and pixel based (JPEG, PNG files). In my test a placed X-4 PDF file worked beautifully until urged to fix it when it is flagged as incompatible with the X-4 output in preflight!! Then you can add to the fail list. In addition (as a result of a fix found that suited our document as files were vectors that didn't reach to page edge so could be cropped) placing files in a picture box and ensure the picture box is entirely on the right hand page by at least 0.3mm, any less and the content disappears. During tests also tried switching from "Trim Box" to "Maximum" or "Minimum content" - which unfortunately alters position of content – another little niggle, even if you have set transform centre to centre.

Looks like this is going no where and getting no improvement. In another attempt to find a cure I discovered that Linked (Remote) files in Publisher show some knowledge of location but odd behaviour. Double click on an image and nothing happens. It doesn't open to edit in Publisher. However, select "Edit Image" in top bar it will open it in a new window. The window will carry the correct file name for the image and can be edited and saved. It doesn't alter its link state or behaviour, and will after saving, in that window, will "reveal in finder". If after opening image in Publisher, in correctly named window, you select "Edit in Photo" it will do so, but transfers as a new file called "<Untitled>" and has to be saved but with no link to original location. –––––––––––––––––––––––––––––- With Linked (Remote) afdesign files the same process ends in file conflicts. Select linked afdesign file and it will open in Publisher new window as above. And you can make edits here. However, Select "Edit in Designer" and this occurs… So still it goes on… Affinity knows where things are but can't communicate it properly if files have been labelled Linked (Remote) I found that if you select all the Linked (Remote) files in the resource manager and Embed them, and then Make Linked, it changes the status and drops the (Remote) tag - but the behaviour of these files remains exactly the same. 🤷‍♂️ ANY CHANCE OF A FIX… THE LARGER THE DOCUMENT THE BIGGER THE FRUSTRATION.

I know that is the outcome, I just find it slightly odd that the resources are not assigned to their specific apps given that you require the full suite for the personas to operate, and that when I see a "publisher" file in the finder I have an expectation of what sort of document that will be, likewise designer and photo. If I’ve edited a JPEG or similar photo and saved as a resource I would expect that file to be an independent .afphoto file for future editing purposes, straight from the Finder - and available to edit in Publisher direct while working on the document file (as it is). If I've placed an .afphoto file and edit it in Publisher and save in, it remains .afphoto. It may well be just me! 🙂

I seem to have regular crashes with working in the Photo Persona of Publisher - no records to share here – but am confused by the file extensions generated. I also like to "live" in publisher for most of the time switching personas rather than apps. If I have a placed JPEG, edit it the Photo Persona and add layers etc, I get the option to save as a new file - which is fine. Why then, does Photo Persona not generate .afphoto resources, instead assigning them .afpub? I know all formats can be read into all apps, but this seems to confuse and often ends up when you edit the resource direct from finder with the apps claiming the file is already open in publisher when it is not and therefore cannot open it.

Very regularly have these seemingly cache related image and type presentation issues. Usually resolved by zooming in and out but can be stubborn. Definitely needs some attention.

I fear this may have shared issues with this that I posted recently…

Clean outcomes can never be guaranteed but the most friendly cross Designer/Illustrator file is undoubtedly a PDF. As illustrator uses the PDF file as a part of its file structure you can change the extension form .PDF to .AI and it will open in Illustrator on an Adobe installed machine. As Pšenda has pointed out non compatible styles will be rasterised. If you've ever tried to open a PDF and strip it or edit it Designer you'll know the kind of thing. Blends that can be created in Illustrator cannot be created in Designer and vice versa, so will rasterise as an image and exist within a vector clipping path, limiting scaling. Vector geometry and flat colours will transfer just fine.

If you place a designer file you first have to select the "Artboard" option rather than "Document" and then you will get the relevant layers pop-up to the left on the context toolbar. I think that having a coloured layer at the back is the best option, but what I am finding in my tests is that each time I update the designer file all layers get turned back on. Rendering the saving on files by only having one linked designer file rather useless. ––––––––––––––––––––––– My suggested workflow for this would be different and utilise the Export persona in Designer, which would allow for a coloured background that isn't exported, and transparent layers over that you could select and export in your chosen format to import into Publisher. If you use continuous export too while working all slices will be regularly updated and automatically imported in Publisher. (Continuous export needs to be rechecked each time you close and reopen the designer file). Changes then made to these layers will be populated throughout Publisher without all becoming all layers as occurs above.

Don't forget that the recently added option to lock the set the position of a new object by option clicking on the positioning buttons top right. Options clicked selection will remain highlighted as shown below. Objects will then be created Behind, Infront or Inside the layer you have selected. With Behind or Infront set as options and no layer selected the new object will be at the very back or at the very front of all layers. Option click a highlighted button to return to default behaviour as described above.

I downloaded your file and exported a PDF in seconds – had to change font though as I don't have SF Pro. Is the font an issue? 2.5.5 on Sequoia too. Techbound monthly mailers.pdf

Some additional reasons why this isn't working so well in another post re dropbox/icloud

I attach a video of some of the crazy broken functionality that I can only assume is linked to this whole remote linked dropbox issue. In a rapid edit (apologies) its a bit quick in parts but essentially two things… Affinity apps are unable to locate resources or files hosted on dropbox Affinity apps are unable to identify and release resources when chosen to Edit in designer/photo …and a myriad more similar scenarios, very frustrating. Affinity and Dropbox - broken.mp4

Great thanks Walt… I didn't recall having to do that double action and the help doesn't explain it that way. I have been happy with Personas most of the time and just needed this level of control and independence – and couldn't make it function. Could do with that sentence and stage being added to the help file I think.

What has happened to this functionality? Having looked this up to check I wasn't going mad, the above is what the help file describes should happen. However what happens is you select an object/linked file in Publisher and select Edit in Designer or Edit in Photo and the entire document opens in the chosen app, not the resource and closes the Publisher file, repurposing it.

@stokerg yes we use the same dropbox account and have done so for many years. I had my partners test this too and the machines show the same issues. Items placed by each of us are fine, items placed by others Linked remote and inaccessible without manually following the link it clearly displays in the resource window. This must be a Publisher bug.