Image* newImage = Image::FromFile(szFileName);
Bitmap image(50, 50);
Graphics graphics(ℑ);
HDC gfxHDC = graphics.GetHDC();
graphics.DrawImage(newImage, 0, 0);
int pixel, row;
for (pixel = 1, row = 1; row <= 50; pixel++)
if (GetPixel(gfxHDC, pixel, row) != RGB(255, 255, 255))
Author
Hello everyone,
I have this code:
Quote:Original post by FromethiusSo what does GetPixel() return? Is gfxHDC valid (Non-NULL)? Your for() loop seems screwed as well, it'll never exit, and you don't use the first row (row 0) or first pixel (pixel 0). What language is this? If it's C++, what API?
Hello everyone,
I have this code:
Image* newImage = Image::FromFile(szFileName);
Bitmap image(50, 50);
Graphics graphics(ℑ);
HDC gfxHDC = graphics.GetHDC();
graphics.DrawImage(newImage, 0, 0);
int pixel, row;
for (pixel = 1, row = 1; row <= 50; pixel++)
if (GetPixel(gfxHDC, pixel, row) != RGB(255, 255, 255))
Anyways, whenever I use GetPixel, the IF statement ALWAYS runs. Even if it is a completely white image. I suspect that either DrawImage isn't drawing it onto gfxHDC or that GetPixel isn't reading the pixels from gfxHDC or I don't even know. The point is, it isn't working and I need some help.
Thanks.
Looks like C++ with GDI+ to me. Does that mean it's managed C++? [EDIT: Apparently not necessarily. Interesting.]
I guessing as I haven't used GDI+, but it is possible that acquiring the HDC for your Graphics object is locking the underlying surface, preventing the following DrawImage() call.
I'd try doing the DrawImage(), then acquiring the device context.
Could be talking a load of rubbish though.
[EDIT] Apparently, and suprisingly, I'm not talking rubbish. The following quote is from MSDN:
BTW, you are releasing the HDC later in the code, right? [smile]
Oh, and Steve's right about your for loop. If you want to loop across the whole image, you need a nested for loop, like:
[EDIT - Interesting stuff, this GDI+]
So I reckon you want:
MSDN does not seem to be forthcoming on whether or not you need to delete the Image that FromFile() returns manually or not (assuming you are not using managed C++).
[Edited by - EasilyConfused on July 25, 2007 6:06:55 AM]
I guessing as I haven't used GDI+, but it is possible that acquiring the HDC for your Graphics object is locking the underlying surface, preventing the following DrawImage() call.
I'd try doing the DrawImage(), then acquiring the device context.
Could be talking a load of rubbish though.
[EDIT] Apparently, and suprisingly, I'm not talking rubbish. The following quote is from MSDN:
Quote:
Each call to the GetHDC method of a Graphics object should be paired with a call to the ReleaseHDC method of that same Graphics object. Do not call any methods of the Graphics object between the calls to GetHDC and ReleaseHDC. If you attempt to call a method of the Graphics object between GetHDC and ReleaseHDC, the method will fail and will return ObjectBusy.
BTW, you are releasing the HDC later in the code, right? [smile]
Oh, and Steve's right about your for loop. If you want to loop across the whole image, you need a nested for loop, like:
for(int Y=0;Y<;50;++Y) { for(int X=0;X<;50;++X) { if(GetPixel(gfxHDC,X,Y)!= RGB(255, 255, 255)) // etc } }[EDIT - Interesting stuff, this GDI+]
So I reckon you want:
void f(){ Image* newImage=Image::FromFile(szFileName); Bitmap image(50,50); Graphics graphics(&image); graphics.DrawImage(newImage,0,0); HDC gfxHDC=graphics.GetHDC(); for(int Y=0;Y<50;++Y) { for(int X=0;X<50;++X) { if(GetPixel(gfxHDC,X,Y)!= RGB(255, 255, 255)) { // do whatever when the pixel is not white } } } graphics.ReleaseHDC(gfxHDC);}MSDN does not seem to be forthcoming on whether or not you need to delete the Image that FromFile() returns manually or not (assuming you are not using managed C++).
[Edited by - EasilyConfused on July 25, 2007 6:06:55 AM]
as mentioned, the if statement isn't really doing anything, other than evaluating a conditional. Try finishing it up, and look at CDC::GetPixel for the API documentation.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
