Add bleed problem

[LasseThid]

I'm trying to create an action list that will add 100 mm of bleed at the foot of the page.

The action works almost as intended, the problem is that the three highlighted rows are not executed for some reason.


Any ideas as to why the trim box and the bleed box wont change as well as why the page marks aren't added?

[loicaigon]

Hi Lasse,

I see that above those lines, you have a "Select objects close to the page edge". That selects…objects, not pages.
And Changing trim/bleed or add trim marks, need a page selection (or pages being part of the selection like in Select All).

If you add either…
- Select All or Select pages all (if it applies to all pages)
- Select pages (range, odd, even…)
- Select page if content is selected (if you want to restrict selection to pages from the currently selected objects)
…before touching page properties, you should be good.

You are an experienced guy so maybe there is something else, but it looks like a probable culprit to me.

Loic

[freddyp]

This is a classic example of not having the correct selection for the action. It is very easy to understand that:

Code: Select all

Select images
Outline text

does not do anything because the selected objects are not relevant for the action. As Loïc already explained, here it is basically the same thing: you cannot change the trim marks of objects close to the edge.

Another classic example:

Code: Select all

Select images
Copy
Paste

That does not work either for the same reason: you can paste on a page, but not on images. A final one:

Code: Select all

Select RGB
Convert color
Select spot color
Add objects to layer
Change trim box
Change document title

You realize it by now: the trim box is not changed, neither is the document title.

Come to think of it, from experience I know that many of the cases that confuse users involve the selection of a page or the document. Loïc, perhaps the actions that require a page or document selection should select it implicitly?

[loicaigon]

@Freddy:

Loïc, perhaps the actions that require a page or document selection should select it implicitly?

What if the actions should only be run on specific pages? Which ones then?

[LasseThid]

Hi Lasse,

I see that above those lines, you have a "Select objects close to the page edge". That selects…objects, not pages.
And Changing trim/bleed or add trim marks, need a page selection (or pages being part of the selection like in Select All).

If you add either…
- Select All or Select pages all (if it applies to all pages)
- Select pages (range, odd, even…)
- Select page if content is selected (if you want to restrict selection to pages from the currently selected objects)
…before touching page properties, you should be good.

You are an experienced guy so maybe there is something else, but it looks like a probable culprit to me.

Loic

Thanks Loïc. Much appreciated!

It was just as easy as that...
I added a Select All and now the action list works as intended.

I blame the fact that it's been a while since I last created an action list.

Sometimes you don't see the trees because of the forrest, as I say...

[loicaigon]

You know, if ever we would rename PitStop Pro, we should call it "Select Pro" , because it's really about selecting the right objects that you want to work with. More than often, something that doesn't work is related to an incorrect selection.

There the Action List Visualizer is also a handy tool for spotting those selection issues.

[freddyp]

@Loïc: you are right of course about the art of selection, but I wonder if the Action List Visualizer will help for the cases where the expected selection is a page object.

This post is not the right place to start a discussion about my suggestion to do an implicit selection of the page for certain Actions. I created a feature request on FeatureOS, the new platform initiated by Loïc for managing feature requests and for letting users participate. I would like to invite forum users who have opinions about this particular feature to do that here:
https://features.enfocus.com/p/implicit ... -selection

[loicaigon]

For Feature Requests, I would indeed invite everyone to go through MyEnfocus. A direct link to FeatureOS might not work.

[LasseThid]

You know, if ever we would rename PitStop Pro, we should call it "Select Pro"

I did use the visualizer for testing the action list, however I still didn't realize why it didn't work...