Jump to content

Recommended Posts

Posted

So 6 YEARS after I first posted this bug it's still not fixed!!!!

Yes the bleed gets exported correctly, but I shouldn't have to export blind and inspect it just to check I've got my bleed everywhere correctly!!! Please Fix 🙏

(the bleed guides are visible, the content within the bleed area is not)

MacBook Pro M1 Max, macOS 12.6.1 Monterey
Affinity Designer : 2.0  Affinity Photo: 2.0,   Affinity Publisher: 2.0

Posted
2 hours ago, iaing said:

I shouldn't have to export blind and inspect it

And you don't have to:

  1. select all content of the artboard
  2. optionally: wrap everything into a layer for convenient handling
  3. in the Layers panel, drag everything outside, on top of the artboard
  4. voilà

But yes, the lack of visible bleed area is definitely a bug, not a "feature".

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

  • 1 month later...
Posted

OMG, this is a six year old issue? I just found out today, that content in the bleed area is not showing and why this happens. That adds to an evergrowing list of why my team is reluctant to switch to Affinity from Adobe for print workflows.

Please fix it, amazing team at Serif/Canva. Thank you! 

Posted

I was searching my lower cheeks off finding a toggle button or something in the settings to turn on the visibility of the bleed section.
Sadly there isn't any.

Now the internet search let me to this forum and a old post from V1. And the search here pushed me to this topic...I am kinda disappointed that this kinda important issue is still not fixed. Hmm...why?

Does anyone know if it's fixed in the beta version?

Posted
1 hour ago, somagfx said:

Does anyone know

In Affinity Designer, artboards are nothing more than container layers. And as with any container, elements cannot protrude from the container frame.

So, the main answer is: No.This is not a bug, but by design

MAC mini M4 | MacOS Sequoia 15.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2605)

Affinity Suite V 2.5.7 & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”

Posted

A bit of disappointment and disagreement, and the explanation provided - while likely technically correct - was not very transparent for all types of customers.

Would it be possible to have a Serif representative clarify this in terms that end users can understand, specifically the difference between artboards and regular pages in relation to the above? It would also be highly beneficial if this were expanded upon in the documentation.

In any case, I find it most credible when a company itself explains what is by design - and why. 

(I am well aware that they usually don’t, but they are here, and I see no point in customers explaining their design choices - only Serif knows.)

Posted
8 hours ago, PROdult said:

A bit of disappointment and disagreement,

An artboard is nothing more than a shape layer where you add other elements as child layers, except that the child layers are automatically inserted in an artboard. And as it is now, it is by design. 
It's best to think of an artboard as a digital sheet of paper; you can't draw or paint anything over its edges.

MAC mini M4 | MacOS Sequoia 15.2 | 16 GB RAM | 256 GB SSD 
AMD Ryzen 7 5700X | INTEL Arc A770 LE 16 GB  | 32 GB DDR4 3200MHz | Windows 11 Pro 24H2 (26100.2605)

Affinity Suite V 2.5.7 & Beta 2.6 (latest)
Interested in a free (selfhosted) PDF Solution? Have a look at Stirling PDF

Ferengi Acquisition Rule No. 49: “A deal is a deal is a deal.”

Posted
1 hour ago, Komatös said:

An artboard is nothing more than a shape layer where you add other elements as child layers, except that the child layers are automatically inserted in an artboard. And as it is now, it is by design. 
It's best to think of an artboard as a digital sheet of paper; you can't draw or paint anything over its edges.

I assumed something along these lines as it also serves as the explanation for an artboard not being able to snap to its child elements.

However this still doesn’t explain why an artboard can be exported with bleed but not displayed. And while the functionality of artboards obviously is by design, it’s a bit of a stretch to claim that their shortcomings are as well. They are just sacrifices being made for some "greater good".

Don’t get me wrong — I really love Affinity’s artboards. However not being able to see what is in a bleed area before exporting might be negligible for some, for others it can mean tedious multiple exports. Mind that exporting large print formats can take its sweet time.

In a world where human designers and artists struggle to compete with machine generated images, videos and music neither "by design" nor "impossible" sound really convincing. Sorry …

Posted
11 hours ago, PROdult said:

a company itself explains what is by design - and why

Here's one:

To work around the missing bleed preview in artboards:

You're welcome. :83_smirk_cat:

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Posted

My stance is, by design, that in such disagreements or debates about A and B, I simply want to hear the company behind it explain why something is by design, whether they originally overlooked something when building the feature, and whether customers’ needs can or will be supported.

Primary sources with exact knowledge always trump secondary and tertiary sources based on assumptions. And they save time. And time is money - for some of us here, at least. I’m here to become smarter, more efficient, and more productive - not poorer in time and money.

By the way, thanks, @loukash 

Posted
30 minutes ago, PROdult said:

My stance is, by design, that in such disagreements or debates about A and B, I simply want to hear the company behind it explain why something is by design

More often than not, when experienced forum users state that something is (likely) "by design", it is quite likely based on an earlier statement by staff. 

Else, feel free to search the forum for older staff statements on a particular topic. Just like I did above.
Caveat: the search result don't show the "Staff" badges (actually they can't: I asked already about it, but apparently there's no such option in the forum software). You may want to look up staff user names here first: https://forum.affinity.serif.com/index.php?/staff

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Posted

I’m generally not very impressed by the experienced forum contributors here. It quickly becomes apparent that many have more experience with the forum itself than with actual graphic workspaces. Regardless, my stance remains the same: I work to create and make money, not to waste valuable time verifying statements from experienced secondary or tertiary sources. And if there are enough questions on an issue, there is enough material for a solid FAQ or scenario-based documentation - created by Serif. It’s unbserious to have to search through a forum.

If some users are so enriched with experience, they can step down from the podium and instead quote the staff directly for such statements from the source - just as you kindly did. That’s a win for everyone. One person’s laziness shouldn’t become another person’s task.

I see a pattern where it’s probably faster and more constructive for us if I write directly to Serif. 🙂  My coffee breaks are too precious to spend in here. 🙂

Posted
1 hour ago, Markus Plutonika said:

still no reasonable explanation

On 2/4/2025 at 11:08 PM, Komatös said:

artboards are nothing more than container layers. And as with any container, elements cannot protrude from the container frame.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Posted
2 hours ago, Markus Plutonika said:

But how can they protrude in the exported PDF then?

Touché! Good point… :) 

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.