On 26 July 2013 18:48, Robin Watts <robin.wa...@artifex.com> wrote: > The cmsContext was introduced a while ago as a way to give *some* thread > safety to lcms. It is by no means a perfect system (as having 2 separate > apps calling into the same lcms library will conflict over their global > settings (*)), but it does solve the problem you are describing.
Of course, thanks! I'll switch to using the THR versions now. What about cmsErrorString()? Worth writing a patch? Richard. ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ Lcms-user mailing list Lcms-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lcms-user
