Le 16/5/2008, "Steve Mills" <[EMAIL PROTECTED]> a écrit:
>Nobody has an answer for this? Supplying the cmsFLAGS_SOFTPROOFING
>flag doesn't make any difference in this respect, but then I don't
>fully understand (nor do the docs explain) why the
>cmsFLAGS_SOFTPROOFING flag needs to be given, when the function is
>called cmsCreatePROOFINGTransform.
>From TUTORIAL.TXT file, you can read:
NOTES: For activating the preview or gamut check features, you MUST
include the corresponding flags
cmsFLAGS_SOFTPROOFING
cmsFLAGS_GAMUTCHECK
This is done in such way because the user usually wants to compare
with/without softproofing. Then, you can share same code. If any of the
flags
is present, the transform does the proofing stuff. If not, the transform
ignores the proofing profile/intent and behaves like a normal
input-output
transform. In practical usage, you need only to associate the check
boxes of
"softproofing" and "gamut check" with these flags.
Hope this helps.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Lcms-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lcms-user
