(v13) The setrealdevice operator
This page applies to Harlequin v13.1r0 and later; and to Harlequin Core but not Harlequin MultiRIP.
As shown in the server loop (v13) The Harlequin server loop, a procedure setrealdevice from serverdict is run after the outer save is established but before the inner save and the job itself is run. The procedure is initially empty. It is provided so that the PostScript-language fragment that is emitted by the %config% device can redefine the procedure to execute appropriate set up for the job in a save / restore context. In the GUI version, this means running the Page Setup selected according to the source of the job.
The %config% device could, of course, execute the set up directly. However, this is undesirable for two reasons:
- The set up would then be permanent, which means items not explicitly reset for the next job would inherit some of the set up from the previous job.
- The set up typically consumes a significant amount of VM; this can be recovered by running it in a
save/restorecontext.
In a core-RIP implementation directly emulating Adobe’s embedded controllers, where eerom is used to store default settings, established by setdefault... procedures (see (v13) Non-volatile settings: eerom), setrealdevice can be redefined to establish these default settings prior to running each job.