Re: resize a bitmap ][
On 27 Nov., 04:13, Joseph M. Newcomer <newco...@flounder.com> wrote:
On Wed, 26 Nov 2008 10:08:15 -0800 (PST), ".rhavin grobert" <cl...@yahoo.=
de> wrote:
BitBlt from *bitmap* to *bitmap* without need of a DC!
Move in same bitmap without need of a DC!
Resize(width,height,offx,offy,DWORD dwFill) with possibillity to
specify a value for new pixels
****
Apparently the idea of using the DC was to allow for hardware acceleratio=
n to be applied
to bitmap operations.
Resize should not need to specify a value for "new pixels" because when y=
ou resize the
image you still have the same image.
we have a mismatch in definitions here. for me: resize != stretch
I'm not sure why the use of the DC is such an insurmountable burden. Crea=
te a memory DC,
select a DIB section into it, move stuff around. Not a big deal.
bool ReplaceHardDrive(UINT nHarddrive)
{
ShutdownSystem();
UnplugSystem();
OpenCase();
bool fRet = RemoveHarddrive(nHarddrive);
if (fRet)
InsertHardDrive(nHarddrive, GetNewHarddrive());
CloseCase();
ReplugSystem();
StartSystem();
return fRet;
}
now, how'd you replace harddrives 1-5?
UINT nHD = 6;
while (nHD-->1)
ReplaceHardDrive(nHD);
?!?
****
Not to think of those simple functions when writing a bitmap-api is so
epically stupid that not allowing OnNcCalsSize() to return a value
seems just a little lapse.
****
What does OnNcCalcSize have to do with bitmaps?
Nothing.