How to Intercept the Built-in 'Print Book' Button on the Book Panel (SDK, C++)

Question

Hi,I would like to add a process when the "Print Book" button is pressed on the Book panel.Is it possible to intercept the button on the built-in panel by adding an Observer?If you have a specific example of how to do this, could you please share it with me?Also, I couldn't find the Boss name of the Book panel and the WidgetID of the "Print Book" button in "BookID.h".Is there any documentation in the SDK where I can find this information?Any help would be appreciated.Thanks,

Dirk Becker · Accepted Answer

Many widget IDs are not published in ID.h files, e.g. kPrintBookButtonWidgetID .

See menu Dev Tools >> Panel Edit Mode of the debug build.

Anyway, would you want to also handle a print action via the fly-out menu, plus e.g. scripted print? Then forget about those widgets.

Along Lawrence' suggestions:

The command kBookPrintActionCmdBoss notifies on the subject of kBookBoss (so no doc observer), protocol IID_IBOOKOUTPUTACTIONCMDDATA. But that's pretty close to when the command is already done.

Remember there are also services, far earlier, e.g. kPrintDataHelperStrategyService (to interfere with Print UI) and kPrintSetupService (more likely to be relevant, see IPrintSetupProvider) …

Dirk

Lawrence Horwitz · Answer

You would not want to deal with panel but rather with the command that is issued when Print Book happens.

You can watch the commands that are sent in the Debug build of InDesign by choosing the menu "Test > Diagnostic > Commands > Trace All Commands > On". You'll need to turn on "Test > TRACE > Command Log" if memory serves, and you'll need to open the Debug Window app from the SDK directory under "devtools".

Once all that's set up, you should be able to figure out the command boss that's being used, and then set up a document observer to catch it and respond to it or attempt to cancel it if you need to.

This is all just scratching the surface. You'll need to look in the documentation at command observers for more detail, and you'll also need to look at the difference between lazy and non-lazy updates.

You can also create a command interceptor, which is less desirable because it has a performance impact, since it affects all InDesign commands, and also opens the door to bugs in other functionality - you need to test it thoroughly. But it allows you to intercept and cancel any command.

Lawrence

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.