Re: Update a graphic and save it

Mike D Sutton wrote:

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.)

Aha - yes. Luckily, in this specific case, I can rely on the fact the
the end-users are running pretty high-end machines with recent
Windowses. Essentially, I'm writing a map-based data manipulation app
to tie in with an upcoming 3D simulator.

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.

Gotcha. I was thinking that the shapes of the individual characters
themselves were being stored as vectors.

Thanks, by the way, for your continuing help. It's very much
appreciated.
.

Relevant Pages
Loading