C / C++ / MFC

BITMAPFILEHEADER bmpHeader;
BITMAPINFO bmpInfo;
FILE *fp = fopen("C:\\test.bmp","rb");
fread((char*)&bmpHeader,sizeof(BITMAPFILEHEADER),1,fp);
fread((char*)&bmpInfo,sizeof(BITMAPINFO),1,fp);

WORD bmpWidth = (WORD)bmpInfo.bmiHeader.biWidth;
WORD bmpHeight = (WORD)bmpInfo.bmiHeader.biHeight;

int counter=0;

fseek(fp,bmpHeader.bfOffBits,SEEK_SET);

BYTE *data = new BYTE[bmpWidth*bmpHeight];
// Read the pixels
while(!feof(fp))
{
  for(int i=0; i<bmpwidth;>  {
    if(!feof(fp))
    {
      fread((BYTE*)&data[counter], sizeof(BYTE), 1, fp);
      counter++;
    }
    else
    {
      break;
    }
  }
}
fclose(fp);

int bytesPerLine = Width / 8; // eight pixels per byte
if (Width % 8) bytesPerLine++; // take into account the reminder

// pad the line to make it to a 32-bit multiple
if (bytesPerLine % 4 ) bytesPerLine += 4 - (bytesPerLine % 4);

// finally you get the size
int iSize = bytesPerLine * Height;

• If you allocate memory of a given size don't trust any other counter (you're using EOF) while filling it: check always you're not exceeding the allocated size (in your code try to read until the allocated buffer is filled and not until the end of the file: if the file contains more bytes your application crashes).
• If you need to read a block, the read it directly, don't read a byte at time.
  



If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Babu@codeproject wrote:

Wat is the difference between closing a dialog by using CDIalog::OnOK() or PostQuitMessage(0).

• post again and again the same question.
• make such stupid and rude replies.

<br />
while(bRunThread)<br />
{<br />
//run mad <br />
}<br />

clawton wrote:

Are there any rules of thumb, guidelines, issues with, etc... about having a return in a catch block

clawton wrote:

Step through the code in debugger.   On several systems, I see the debug statement indicator move onto the line with "return 1".  

clawton wrote:

The disassembly code is very strange indeed