Should Publisher "see" Designer's bleed or not?

[Vosje]

Hello, I was wondering what your thoughts are about using bleed across different Affinity apps. I've encoutered something that I expected to work otherwise, but maybe it's actually good that it works the way it does?

If I create a document of 20 x 30 cm with 3 mm bleed and facing pages in Publisher and then I need an illustration that will cover the whole spread, I thought that it's good to go if I create a document in Designer with similar settings: 40 x 30 cm and 3 mm bleed. For whatever reason I thought that Publisher will "see" Designer's bleed settings and will include it when I place Designer file into Publisher. And that both bleeds will kinda overlay eachother so the final result that you will see is an image of 40 x 30 cm.

However that didn't quire work that way, Publisher just ignored Designer's bleed settings, only used the working area of 40 x 30 cm and so the image was scaled a little bit when I placed it in Publisher (because I placed it in the area of 40,6 x 30,6 cm that includes bleed on both sides). So in the end I had to resize my Designer image and make it 40,6 x 30,6 cm without any bleed.

So my question is, is there maybe a setting somewhere to tell Publisher to include Designer's bleed when you place an image? Maybe is some situations you'd want the other app to be able to include it (while for other situations it's better not to).

[loukash]

1 hour ago, Vosje said:

However that didn't quire work that way, Publisher just ignored Designer's bleed settings

Isn't this a bug that may have been fixed in the current public beta?

On 12/7/2022 at 2:30 PM, AdamW said:

- Placed documents with bleed can fail to render the bleed correctly

^ from 

 

[Vosje]

Thanks for the link, @loukash! The description does sound like this can be exactly the issue I'm talking about! I guess I'll just have test the new release & see if it behaves differently.

[loukash]

Just now, Vosje said:

I'll just have test the new release & see if it behaves differently.

That's the very purpose of public beta tests.  

[lacerto]

On Windows. at least, I could not see any change in behavior between the release and the latest public beta v2. Now that I tested the feature more thoroughly it has become significantly worse in version 2. Only trimmed design (of Designer document) can be placed in Publisher, and if that document has bleeds defined, the trimmed area is shown all wrong. Even placing the design as a document does not work. In version 1 Designer artboards were shown correctly in Publisher (even if bleeds were cut off), and any artboard could be used with bleeds if placed and positioned in Publisher as a document. Now it is a complete mess. I have not checked yet how this works on macOS.

EDIT: I later had a test run on macOS (Ventura, M1), and release version 2 (not beta) and it is similar there, or even worse. I could not e.g. select which artboard to show of a placed Designer v2 file containing multiple artboards (the first one is always shown). Also, even Designer v2 files with bleed defined but not having any artboard at all could not be shown correctly.

Beta testing is kind of nightmare at the moment. I had version 1, version 2 release and version 2 public beta running concurrently (both Designer and Publisher so 6 apps), and additionally Photo version 2 release. They all became non-responsive after one of the version 2 apps became (even if no longer shown to be non-responsive in Task Manager) simultaneously, and after having been killed, none of Affinity apps, even version 1 ones, would relaunch properly without rebooting the computer. This would certainly be the foremost bug to tackle! 

[loukash]

33 minutes ago, lacerto said:

I had version 1, version 2 release and version 2 public beta running concurrently (both Designer and Publisher so 6 apps), and additionally Photo version 2 release. They all became non-responsive after one of the version 2 apps became

I had all 9 open and was testing them last night on my "antique" MacBook Pro mid-2012, booting from a Catalina partition. Apart from crashes documented in this thread there, no problems whatsoever. 

So that would be a Windows issue I guess.

[lacerto]

41 minutes ago, loukash said:

So that would be a Windows issue I guess.

Yes, it definitely is. Version 1 apps never crashed this way, and when becoming non-responsive, this status always showed in Task Manager, and tasks could be terminated orderly and immediately relaunched without issues. I am not sure if it is related to having two different framework apps (UWP and WPF) of the "same" app running concurrently, or if this happens also when running version 2 apps alone.

[Vosje]

5 hours ago, lacerto said:

Now that I tested the feature more thoroughly it has become significantly worse in version 2.

Wow @lacerto, you've even tested it already, many thanks!!! That's a real pity it has actually gotten worse than before... 😣 Guess the bugs forum will become yet another thread richer! That's also a pity you're experiencing issues with crashing/hanging you haven't before, I for now stick to v1, purchased v2 but I feel like has too many issues for now so I'm waiting for an update...