Preflight settings to exclude checking hidden objects "command + 3" and hidden layers

[mattiaso33135605]

Hello.

Is there a way to configure a preflight setting so it olnly checks visible objects and layers, excludes hidden objects and turned of layers?

Best regards Mattias

Teamleader

Stibo Complete AB

Sweden 

[leo.r]

I don't believe you can do this natively.

corrected below

[mattiaso33135605]

But you think you can do it in another way? A script?

[leo.r]

But you think you can do it in another way? A script?

By @mattiaso33135605

Wait, actually there's a built-in way to do this, at least partially:

[mattiaso33135605]

No unfortunately that doesnt work, its only for layers.

My objects are on the same layer but they are hidden with the command + 3 function.

The option should be Exclude hidden objects and hidden layers.

[leo.r]

P.S. Hidden objects will still be preflighted, you'll need to mark your hidden objects as 'Nonprinting' in the Attributes panel. This can be scripted relatively easily, at least much easier than creating an entire custom preflighting script.

[mattiaso33135605]

Sounds good.

I need to explain our situation/workflow a little more.

We use a populating plug in Easy Cataloge from 65Bit https://www.65bit.com/software/easycatalog/

we use templates that are show/hides different elements depending of the input with rules.

The benefit from hiding objects from deleting them is that if it changes in the manuscript/data source the template can change to the appropiate apperence that meets the requirements. But we dont want all that hidden objects to be included in the preflight check because then we get so much warnings, especially of overflowing text.

[m1b]

@mattiaso33135605 Would this be a good use of Conditional text and Conditional Sets ? These provide handy ways to hide and show different things but it depends on your specifics. 
- Mark

[mattiaso33135605]

Hi!

I need to explain our situation/workflow a little more.

We use a populating plug in Easy Cataloge from 65Bit https://www.65bit.com/software/easycatalog/

we use templates that are show/hides different elements depending of the input with rules.

The benefit from hiding objects from deleting them is that if it changes in the manuscript/data source the template can change to the appropiate apperence that meets the requirements. But we dont want all that hidden objects to be included in the preflight check because then we get so much warnings, especially of overflowing text.