Re: MagickSetImageType and gm convert: inconsistent behaviour

On Tue, 28 Sep 2010, Graham Leggett wrote:
>
> Would it make sense to introduce a new API function, say 
> MagickSetSavedImageType() and MagickGetSavedImageType(), which operates on 
> wand->image_info->type directly?
>
> In this way, the gm convert function can use MagickSetSavedImageType(), and 
> work as it does now, and the MagickSetImageType() would remain unchanged.
>
> In this way, the API remains unchanged for existing code.
>
> Would this be workable?

I would like to see if ImageMagick's Wand library has made any special 
provisions for this issue.  If ImageMagick has already set a precedent 
then it would be good to follow it in order to cause the least 
surprise for ImageMagick Wand users.

What you say seems reasonable except that it is also likely that a few 
format writers (there are many!) do not respect the ImageInfo type 
field but do output a subformat suitable for the current image 
representation.  This would be an argument to immediately adjust the 
current image representation based on the type request.

Research is required.

Bob
-- 
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev