CAPS Universe documentation  1.0.4
All you need to know to be successful
Callback exit()

Everything you need to clean up.

  • parameter you get
    • framework handle
    • your private data hint
  • you can expect as already done
    • connection to the printing coordinator is already closed
    • communication to the printer is still possible, but only if the printer device is still online. Since most of the time a gone printer device is the trigger to terminate the driver, you shouldn't expect a working communication with the printer. You can use caps_drv_is_offline() to distinguish this case.
  • what you must do
    • prepare your printer device to shut down (power saving mode for example) if it is still online
    • memory clean up (to avoid false positives when running with a memory leak checker for example)
  • values you should return
    • 0 everything is okay, the framework can continue
Note
This callback is optional.