Lines Matching refs:handler

260 You will also need a structure representing a JPEG error handler.  The part
262 are providing your own error handler, you'll typically want to embed the
265 handler.  The default error handler will print JPEG error/warning messages
268 You must initialize the error handler structure, store a pointer to it into
272 Typical code for this step, if you are using the default error handler, is
281 if you are out of memory.  In that case it will exit via the error handler;
282 that's why the error handler must be initialized first.
477 handler structure.
766 On some systems your application may need to set up a signal handler to ensure
770 freed automatically.  See cjpeg.c or djpeg.c for an example signal handler.
774 error handler need it.  You can use the library in a stdio-less environment
1273 When the default error handler is used, any error detected inside the JPEG
1300 "err" field.  Frequently, custom error handler routines will need to access
1302 handler.  The most convenient way to do this is to embed either the JPEG
1340 library; the other two are internal to the error handler.
1351 handled by the same mechanism.  The error handler supports a second "add-on"
1359 Actual invocation of the error handler is done via macros defined in jerror.h:
1364 error handler struct, then invoke the error_exit() or emit_message() method.
2805 managers, it's a good idea to provide a signal handler that will trap any
2806 early exit from your program.  The handler should call either jpeg_abort()
2807 or jpeg_destroy() for any active JPEG objects.  A handler is not needed with
2953 handler, all of which are application-replaceable.  (cjpeg/djpeg are more