[gs-commits] rev 10908 - trunk/gs/base

robin at ghostscript.com robin at ghostscript.com
Wed Mar 10 12:51:50 UTC 2010

Author: robin
Date: 2010-03-10 12:51:50 +0000 (Wed, 10 Mar 2010)
New Revision: 10908

Change the condition under which we update the overprint device when restoring
a graphics state to be more relaxed; rather than updating if the overprint
state has changed we now update if it was enabled, or it if it is enabled.

The logic behind this is that it will still fire in all the same conditions
it did before, but will also fire when we restore from a state that had it
enabled to another state that had it enabled. This should be entirely
harmless, but will allow the state to be updated in the case where a
colorspace has been updated.

This causes 2 differences in the tests, that only show up in psd files.
All indications seem to be that these files really are identical. But if
they aren't, I believe they should be progressions, rather than regressions.

This moves the trunk more into line with the output of the gs_2_colors branch.

Modified: trunk/gs/base/gsstate.c
--- trunk/gs/base/gsstate.c	2010-03-10 11:32:39 UTC (rev 10907)
+++ trunk/gs/base/gsstate.c	2010-03-10 12:51:50 UTC (rev 10908)
@@ -411,7 +411,7 @@
     gs_free_object(pgs->memory, saved, "gs_grestore");
     /* update the overprint compositor, if necessary */
-    if (prior_overprint != pgs->overprint)
+    if (prior_overprint || pgs->overprint)
         return gs_do_set_overprint(pgs);
         return 0;

More information about the gs-commits mailing list