🚀 go-pugleaf

Well, my report is based on several Microsoft articles
that accept responsibility for the bugs, working in the
Windows graphics industry since Windows verison 0.8 beta,
and supplying graphics engines to some of the top guns of
the desktop publishing graphics industry, and finally manning
the support lines at Borland for some time.

Of course, I could just be nuts<g>

Joe
--
Delphi, graphics, and printing specialist available - $35/hr
http://www.code4sale.com/codeit/index.htm

"Adam Versteegen" <no@email.com> wrote in message news:3e9cc7e0@newsgroups.borland.com...
> Joe C. Hecht wrote:
>
> > We tried using EnumEnhMetaFile (and the non-enhanced version) for a simple
> > metafile that would lock up 95/98 and ME machines. Turned out the even
> loading
> > the metafile (without eenumerating) using Windows functions would result
> in severe
> > memory leaks.
> >
> > We feel it is best to read the file raw, and enumerate them yourself
> (although the docs are
> > often incomplete or totally incorrect).
> >
> > Joe
>
> I'd actually check the metafile you're using as opposed to the metafile
> functions.... I've had no problems with the functions (and use them quite
> heavily) provided that the metafiles i'm using are ok. Adobe Illustrator is
> one application that produces bodgy files. Unless you get down to the nitty
> gritty and make sure that it is freeing all it creates, if you try
> repeatedly drawing these metafiles using any of the API calls you will
> notice GDI resources vanishing before your eyes (which will lead to
> lockups). I've found that metafiles that I create myself (using VCL
> components) are fine and do follow all the proper rules.
> If you do an enum on an illustrator file, you can see from the records it
> spits out that they fail to clean up after themselves... Other programs may
> do the same.
>
> Vesty.
>
>