I got bored. Multi-frame images should work now. Formats with multi-frame capabilities now always get written out as multi-framed images. There is a really easy way to disable this (via a boolean argument to a constructor/method) but no UI to handle this yet.
I also now pass UTF-8 strings to the drawString and measureChar functions. Hopefully I'm not screwing anything up. Possibly also need to push another drawable type that doesn't yet exist. AbiMagick's Image importer/reader now has fairly adequate suffix recognition instead of just returning "UT_CONFIDENCE_GOOD". CVS: ---------------------------------------------------------------------- CVS: Enter Log. Lines beginning with `CVS:' are removed automatically CVS: CVS: Committing in . CVS: CVS: Modified Files: CVS: wp/impexp/graphics/magick/xp/AbiMagick.cpp CVS: wp/impexp/graphics/magick/xp/MagickGraphics.cpp CVS: wp/impexp/graphics/magick/xp/MagickGraphics.h CVS: ---------------------------------------------------------------------- On Sunday, August 18, 2002, at 10:55 AM, Dom Lachowicz wrote: > I am not planning on dealing with formats like GIF, TIFF, PDF, PS > which support multiple frames/pages per document at this time. If you > want it anytime soon, you do the work. > > I'll perform a UCS-4->UTF-8 translation for the strings in > anticipation of things working properly, which I'm not wholly > convinced that it will. The C++ interface certainly doesn't support a > DrawableEncoding type, at least not yet. > > Dom > > On Sunday, August 18, 2002, at 08:25 AM, Leonard Rosenthol wrote: > >> At 10:57 AM -0400 8/17/02, Dom Lachowicz wrote: >>> Right now it is accessible from "File->Print to Image". It prints an >>> image per page of the document. For example, if your document is >>> titled "Hello World.txt" the first page will be "Hello >>> World.txt_1.png". With a little bit of work, we'll be able to pop up >>> a dialog box and be smarter about things (choose file names, choose >>> output format, ...). >> >> You also need to deal with formats (like TIFF) which support >> multiple images per document. >> >> >>> I also forgot that I didn't see a way to pass a unicode string to >>> IM's Drawable class, or even a string with an associated encoding >>> (eg ISO-8859-2 or UTF-8) which would be an acceptable work-around. >>> I'll see what I can do about this. >>> >> >> IM supports UTF-8 encoded text strings for the drawing commands. >> >> >> Leonard >> >> -- >> ---------------------------------------------------------------------- >> ----- >> Leonard Rosenthol >> <mailto:[EMAIL PROTECTED]> >> <http://www.lazerware.com> >
