Re: Update a graphic and save it
- From: "Mike D Sutton" <EDais@xxxxxxxx>
- Date: Mon, 22 May 2006 15:08:58 +0100
Interesting, Mike - thanks. To be honest, I hadn't considered memory
usage as a significant factor in my own app - it seems to work pretty
well at creating large bitmaps using the PictureBox method, even on
this seriously underpowered PII laptop I'm using at the moment.
Try running the app on a Win9x/ME box, you may well find that it fails if you're using Bitmaps larger than ~16mb (IIRC
16mb was for Win95/8, not sure about WinME but it also had a pretty low limitation.)
Also, I didn't realise that Terry's data was vector-based. How
efficient is that at storing text? I'd have thought that a compressed
raster format would be smaller for text-heavy images - but I'm by no
means an expert.
EMF is very efficient at storing text, since only the text string and font information are stored - The playback engine
converts this back into full vector outlines at the desired size/weight then rasterises that. This does however mean
that EMF is slower as rendering since everything has to be rasterised every time it's drawn, however this is the case
for any resolution independent format and in this case pretty much irrelevant.
Mike
- Microsoft Visual Basic MVP -
E-Mail: EDais@xxxxxxxx
WWW: Http://EDais.mvps.org/
.
- Follow-Ups:
- Re: Update a graphic and save it
- From: John Hatpin
- Re: Update a graphic and save it
- References:
- Re: Update a graphic and save it
- From: Mike D Sutton
- Re: Update a graphic and save it
- From: Terry
- Re: Update a graphic and save it
- From: John Hatpin
- Re: Update a graphic and save it
- From: Mike D Sutton
- Re: Update a graphic and save it
- From: John Hatpin
- Re: Update a graphic and save it
- Prev by Date: Re: Update a graphic and save it
- Next by Date: Common Interface for objects that expose VB-drawing-API
- Previous by thread: Re: Update a graphic and save it
- Next by thread: Re: Update a graphic and save it
- Index(es):
Loading