Am 08.06.08, 12:56 +0200 schrieb Kai-Uwe Behrmann: > Am 08.06.08, 18:49 +1200 schrieb Guy K. Kloss: > > On Fri, 06 Jun 2008 9:01:41 pm Kai-Uwe Behrmann wrote: > > > Cant you raise the exception simply in the cmsErrorHandlerFunction > > > provided by you, by checking ErrorCode and reacting on LCMS_ERRC_ABORTED? > > > > Once I do this from one part in my program, another part of the program (e. > > g. > > in a different thread) would overwrite the error handler or it wouldn't > > receive any exceptions, as the other registered error handler function > > would. > > Plus the error handler would be detached of the context of the calling > > instance, rather than that the context itself could handle what to do in > > case > > of errors. > > Well, I'd say the only help would be to thread the library work itself and > allow only one thread/instance to work with the library. This > suggestion ends not in a real parallel computing with intermixed contexts, > but at least goes as far as a non context aware library allowes. As > context I would understand anything from a user selected ID to a pointer, > which can later be mapped back to a object.
Forgot to mention: To make the lcms error function context aware, it would have to deliver the user supplied context as well, not only code and message. The context should be attachable to the transform building and the transform run, as these are the stages where processing occurs. > Hope both the limited workaround and the context design are reasonable. kind regards Kai-Uwe Behrmann -- developing for colour management www.behrmann.name + www.oyranos.org ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
