Named notification for printing complete

[KennethAa]

Hi,

We need to implement logging of printed documents in our application, but as far as I can see, there is no way to detect when the user has printed the open document. Can you please add a named notification (like the TextEditor::OnStart/OnStop notifications) for when the document has been sent to a printer, ie after OK in the print dialog?

Best Regards,
Kenneth Aafløy
In3 Support AS

[Vasyl - PDF-XChange]

This feature will be added into the next build (upcoming).
For this, you should catch OnEvent(PXCVA_OnNamedNotify, "Notifications.Print", ...)
For details, refer to "Reference\Named Items\Notifications\Print" in the new SDK Help file that will be updated for the new release.

[DSSavant]

As a follow-on question, once the document has been printed, is there a way to find out what Pages of the document the user decided to print. I need to audit that the user printed the document (as compared to pressing Cancel within the print dialog) and what exact pages where printed. Further, the printer name would be nice but not necessary.

[John - Tracker Supp]

Hi,

I am afraid we offer no specific mechanism to achieve this and unless you code some very restrictive interface or capture method its going to be very tough and cumbersome to achieve.

[Vasyl - PDF-XChange]

Hi, DSSavant.

...I need to audit that the user printed the document (as compared to pressing Cancel within the print dialog) and what exact pages where printed.

You may:
1. setup print-events filter:

Code: Select all

SetProperty("Notifications.Print.Filter", -1, 0); // to listen all print-events

2. and catch the print-event:

Code: Select all

OnEvent(Type:PXCVA_OnNamedNotify, Name:"Notifications.Print", ...)
{
	if (Notifications.Print.Type == "EndPage")
	{
		GetProperty("Notifications.Print.PrinterName", prnName, 0);
		GetProperty("Notifications.Print.Document", docId, 0); // document which printing
		GetProperty("Notifications.Print.Page", pageIndex, 0); // page which printed
		//
		// collect obtained info into your history...
		...
	}
	...
}

HTH

[DSSavant]

The Event catching method should work ... I hope. Thanks.

Allow me to suggest a few items for your next release:

- Ability to Audit user actions more closely and in a more streamline fashion. If at all possible, using OOPs paradigms.
- Printing, Rotating, Extraction, Page movement, etc. All changes to a document should be able to be audited. I would be willing to bet that people are using the SDK because they need this type of granularity as compared to simply embedding a PDF editor in their application.

-------------

As a follow-on, I noticed that when you call the Print Document function, it will throw if the user hits cancel. Pressing cancel is not an error condition so I would not expect it to throw. Maybe the routine should be returning something like a DialogResult instead?