'image-color' rc function being completely ignored

[Peter TB Brett]

When using "File->Write image..." to export an image, the "image-color" rc function has no effect on whether the output is in color or not -- the result will always be a color image (using the display color map for raster images and the print color map for PDF images).

The "image-color" setting should obviously be observed. Also, all images should be exported with the same color map (but should it be the display or print color map)?

[gpleda.org commit robot (gpleda-launchpad-robot)]

A commit was made which affects this bug
git master commit ba3e5f3c73f3a6333eaac64977077a6308bbbbb6
http://git.geda-project.org/geda-gaf/commit/?id=ba3e5f3c73f3a6333eaac64977077a6308bbbbb6

commit ba3e5f3c73f3a6333eaac64977077a6308bbbbb6
Author: Peter TB Brett <email address hidden>
Commit: Peter TB Brett <email address hidden>

    Remove TOPLEVEL.override_color.

    It's not actually used by anything. To override the color used for
    rendering, the "override-color" property of EdaRenderer should be used
    when renderering. Exposes bug in gschem image export color handling.

    Affects-bug: lp-1086530

[Peter TB Brett (peter-b)]

Okay, so this is the current behaviour relative to the image-color setting:

image-color Format Result
=========== ====== ======
disabled PNG Greyscale version of display colour map.
disabled PDF Monochrome print colour map.
enabled PNG Display colour map.
enabled PDF Colour print colour map.

What exactly is the expected behaviour here? Should image export always match the display colour map, or always match the print colour map? What should happen in the (image-color "disabled") case?

My thoughts:

1) With (image-color "enabled"), the display colour map should be used.
2) With (image-color "disabled"), the monochrome colour map should be used.