Jump to content
You must now use your email address to sign in [click for more info] ×

Objects to "No Print"


Recommended Posts

  • 4 weeks later...
  • 1 month later...
  • 3 months later...

+1 for non-printable (global) layers too

I may not need them in each publication, but when I need them they're really needed.

An alternative might be to create a draft layer type, Clip Studio Paint has this and it will never be exported when publishing to several file format (in this case image formats like TIFF, JPEG etc.). The intent for this layer is to keep draft sketches, lines, mockups etc. visible but never publish them. Basically this is the same as setting a global layer to non-printable but it does this automatically because of its layer type.

Link to comment
Share on other sites

+1 

Mac mini M1 A2348 | Windows 10 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

 

Link to comment
Share on other sites

  • 8 months later...

A relatively easy workaround is to add a Preflight Comment to every object you don't want to print. On export or print, preflight will warn you so that you don't forget to hide those objects.

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

Link to comment
Share on other sites

23 minutes ago, EmoSludge said:

Not really a workaround.

It really is a workaround. It's the sheer definition of workaround: we're working around a missing feature.

But you can also just sit there, hold your breath and wait for Serif releasing the Publisher update in three, two, one…
Your choice. ;) 

20 minutes ago, EmoSludge said:

I'm trying to save myself the step of turning off and on layers to export

We all do.

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

Link to comment
Share on other sites

1 hour ago, loukash said:

A relatively easy workaround is to add a Preflight Comment to every object you don't want to print. On export or print, preflight will warn you so that you don't forget to hide those objects.

Extending that workaround idea, you can create a Master Page and a Layer on it to hold the items you won't want to print. Then you can simply Hide that Master Page Layer before Printing or Exporting, and Hide all that stuff with one action.

You will probably need to become familiar with using Edit Detached to add items to that Master Page Layer when appropriate.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1

Link to comment
Share on other sites

7 minutes ago, walt.farrell said:

you can create a Master Page and a Layer on it to hold the items you won't want to print.

There are many possible workarounds. You can also use named objects or a specific layer tag, then use Select Same (in APu v2 only) to disable them all with one click.
The benefit of Preflight comments is the error warning on export and print. It's active in the Default preflight preset.

That all said…
@EmoSludge, what's the point of bumping a v1 Feedback thread anyway? There won't be any new features added to v1.

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

Link to comment
Share on other sites

  • 9 months later...
On 1/20/2023 at 6:58 PM, loukash said:

what's the point of bumping a v1 Feedback thread anyway? There won't be any new features added to v1.

That is an absurd comment. You should be directing this question to Affinity, not a user. Do you expect users to log in, year after year, and re-post their feature requests under new version numbers to herd them along in perpetuity?

Link to comment
Share on other sites

31 minutes ago, Stokestack said:

Do you expect users to log in, year after year, and re-post their feature requests under new version numbers to herd them along in perpetuity?

Yep.

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

Link to comment
Share on other sites

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.