Re: Text overlay on image then Save to JPEG with reasonable DPI for Online printshop

"Rob" <robnews@xxxxxxxxxx> wrote in message
news:4381ebbf$0$11076$e4fe514c@xxxxxxxxxxxxxxxxx

> Let's suppose I have an image of 1500 X 1500 pixels of which I
> make the template I want to display this image in my application at
> 527 X 338 pixels ( 14 X 9 cm)

Okay. I'm still not quite sure whether your starting image is the small
picture at the top right of the card, or whether it is actually the card
itself (or indeed whether either of those things have got anything to do
with it at all) but basically when you are writing code to edit images you
*always* work with the *full size* original image and you always do all of
your edits on the full size image. That full size image is usually hiden in
memory (an invisible VB picture box or a memory bitmap or DIBSection or
whatever). What you "display to the user" while he (or your own code) is
editing this full size image is up to you, but typically you might show him
a "reduced size" copy of the "invisible" large image that he (or your code)
is editing. Normally the user never actually sees that large image at all.
It is kept hidden in memory. All he ever sees is the scaled down version of
it that you are currently showing to him (unless, of course, it is a full
blown editing program you are writing which would amongst other things
include the ability for him to view and scroll around the full size image).
These things require very much less code (and are therefore much easier to
program) if you use a VB picture box to hold the full size image, but if
your code is to run properly using full colour images even on machines that
are running at less than full 32 bit Windows display depth (16 bit, for
example) then you will need to use memory DIBSections instead. This is a lot
more work "coding wise", especially if you want to load in original jpeg
images, so the first question I would ask you (before I go any further into
explaining this stuff) is, "Are you happy to expect your users to always run
their machines at full colour depth (the more or less "standard setting"
anyway these days) and, if not, are you prepared to accept the slight loss
of colour quality that would occur if they ran their machines at (say) 16
bit colour depth. If the answer to those questions is "Yes" then it makes it
all very much easier, because you can use VB picture boxes instead of memory
DIBSections. Also, what do you mean by "1500 x 1500 pixel original". Is that
the size of the entire image (including the "card" if that is also part of
the image)? Also, one final question, why would you want to show a 1500 x
1500 pixel picture (a 1:1 aspect ratio) on the display at a size of 527 x
338 pixels (an approximate 1.5:1 aspect ratio). Sutrely that would distort
the picture (make it "quite a bit fatter"). Or have I perhaps misunderstood
part (or indeed all!) of your question?

Mike





.