|
Building Scan Lines
The file parser builds the scan line data as a continuous stream of bits that
define each pixel. Each pixel is packed into an array of bytes in such a way
that if the data were written out in hexadecimal or binary numbers, the pixels
could be read in order from left to right. That is, for a 4-bit-per-pixel format,
the first pixel is stored in the high-order bits of the first byte (bit 7, bit
6, bit 5, and bit 4), and the second pixel is stored in low-order bits of that
byte (bit 3, bit 2, bit 1, and bit 0). Thus, if the first eight pixels of a
4-bit-per-pixel scan line have the hex values of 0, 2, C, 9, A, 4, 3, and F, the
first four bytes of scan line data would be 02, C9, A4, and 3F.
If the parser provides a palette for the image, the data for each pixel is
interpreted as an index into the palette. If no palette exists for the image, the
bits for each pixel specify either a true color (24-bit only) or a gray scale
value. For 24-bit color, each 3 bytes of a scan line represent the intensities
of red, green, and blue of a single pixel.
When the scan line has been completely specified, the parser must call SOPutBreak with the SO_SCANLINEBREAK value, except for the last line of the bitmap. The
last line of the bitmap must end with a break of the SO_SECTIONBREAK or
SO_EOFBREAK type, whichever applies.
The following example illustrates the use of the bitmapped functions in the
simplest possible case: a parser with scan line data stored one tile wide and
with the same format that parsers are required to provide it, so the data requires
no additional processing after being read in. This example also does not check
for EOF or read errors.
WORD wBytesRead;
WORD wBufSize = Proc.ScanLineBufSize;
do
{
...
xread( hFile, Proc.ScanLineBuf, wBufSize, &wBytesRead );
SOPutScanLineData( Proc.ScanLineBuf, hProc );
...
} while( SOPutBreak( SO_SCANLINEBREAK, 0, hProc ) == SO_CONTINUE );
| Last news from Greatis Software |
 |
|
Nostalgia .Net |
|
.Net is powerful, but not all-powerful, so sometimes we need to use Win32 API for our .Net applications. It's simple enough with Platform Invoke if you have Win32 skill, but we do not always have time to dig the ancient documentation, declare the special types that are compatible with Win32, find the values of the Win32's constants and so on. Nostalgia .Net offers several simple-to-use classes, and components that will allow you to forget about the headache of Win32 and just use the power of Win32 in your application the same way as you use the native. Net classes. More » |
| Recommended software for developers |
 |
|
Ultimate Pack |
|
Component pack for Delphi and C++ Builder that contains runtime form designer, runtime object inspector, print suite and much more for the very special price. More » |
 |
|
Form Designer .Net |
|
Unique runtime form design solution that allows to edit any form in .Net WinForms application at runtime with full source codes for only 300 euro! More » |
 |
|
Print Suite .Net |
|
Print Suite .Net is a set of components for easy printing texts, images and grids from your WinForms applications. Full C# source codes are available More » |
 |
|
Gradient Controls .Net |
|
Gradient Controls .Net offers controls with gradient background feature. Labels, panels and so on... Full C# source codes are available More » |
 |
|
Greatis iGrid |
|
iGrid plots drawing grid right over your desktop, so you can use it everywhere, with any drawing application without any special plugins for different graphic editors. More » |
All the contacts and projectsDmitry Vasiliev (just.dmitry)
Related LinksSoftware for Visual Studio .NET developers
Software for Delphi and C++ Builder developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET More Online Helps Win32 Programmer's Reference
Win32 Multimedia Programmer's Reference
OLE Programmer's Reference
Microsoft Windows Pen API Programmer's Reference
Microsoft Windows Sockets 2 Reference
Microsoft Windows Telephony API (TAPI) Programmer's Reference
Unix Manual Pages
|
