I cannot get the presstalk procedure stopjob() to work when using a user-defined emulation.

Interpretation of the form continues as if stopjob() were not present (in preview, on printer and in Image).

I need to stop the job to workaround other issues caused by user-defined emulation misbehaving with version 5.3.1.2324. Is there any other way I can stop the job?
Thanks
Stuart

I have found another way to stop printing - I set a variable and now every page only executes if the variable is set.

That still leaves the question of why stopjob() doesn't work.

Stuart

stuartg,

I did not find anything wrong with the setjob() command. It may have been your condition that is wrong. I tried it in the user-defined emulation, in a PressTalk object and in the PlanetPress talk after the page, and everything works fine.

If you used it in the user-defined, did you make sure you at least got one page of data? Because if you use stopjob() before getting at least one page of data, it will create an empty document and it will not work.

Regards,
Rapha

I think the user defined emulation is a red herring.

I've investigated further and stopjob() does not behave as documented.
The doc says
"Terminates execution of the document and returns control to the PostScript interpreter."

On this basis I expected it to print the current output page and then stop execution of the document. What it actually does is stop reading further input data. It continues to process and print any more output pages from the current input page.


If my doc has multiple output pages from one input page eg.

Page 1
Stopjob()
Page 2
Page 3

Then page2 and page3 are printed even with the stopjob().

I suggest that if stopjob() is working as intended then the PP5 documentation needs amending to match.
regards
Stuart