DibDraw( hDC, hMemBitmap, hPalette, nRow, nCol,;
                                     nWidth, nHeight)-> <lSuccess>
--------------------------------------------------------------------------------


 PARAMETER:

  <hDC>               handle that identifies a device context

  <hMemBitmap>        is the handle of the BitMap

  <hPalette>          is the handle of the palette associated to the BitMap

  <nRow>,<nCol>       The coordinates in pixels where the drawing
                      will start

  <nWidth>,<nHeight>  The dimensions for drawing the Bitmap


 RETURNS:

  <lSuccess> will be TRUE if the operation was successful.


 DESCRIPTION:

  This function draws a DIB (device independent bitmap) on the device
  context specified by hDC. 

  When we started building FiveWin we first started working with bitmaps.
  Later we discovered, that the general recommendation was to work with
  DIBs, so we developed all the necessary functions to work with them.
  And then we experienced, that there was a different way (a mixture 
  between both ways ), that was much faster and easier to handle.

  We did a lot of different tests, and our way was by far the fastest, so
  this is the way we go with FiveWin, though we also offer support for
  Bitmaps and DIBs managing.

  You don't have to worry at all for all these, just use FiveWin's 
  TBitmap Class to get the maximum productivity


 SOURCE:

  SOURCE\WINAPI\DIB.C