considered that, but the CreateDIBSection documentation is confusing. On the one hand,
ppvBits [out] pointer to a variable that receives a pointer to the location of the DIB bit
which is what I would need, but then it says
hSection [in] ...if hSection is NULL, the system allocates memory for the DIB. In this
case, ... an application cannot later obtain a handle to this memory.
This seems to suggest that you cannot get hold of the memory that is used for the bitmap,
and at 5am I did not have enough functioning neurons to figure out exactly how to resolve
these two apparently conflicting statements. I have no idea why I would want a handle
when I clearly specified as NULL, or why I should be surprised if, later, I ask for it and
it tells me exactly that the handle I provided was NULL, but what does this have to do
with the ppvBits parameter? The documentation seems to be going out of its way to tell me
about something I clearly do not care about, and consequently the documentation doesn't
make any sense. If I give a handle of NULL for a file-mapping section, why would I have
the slightest interest in getting this NULL handle back? Why would I even care about
getting a handle to something that clearly is irrelevant?
Could it be that CreateDIBSection, if I give a NULL handle, creates a file-mapping object
for me? If so, why should I care about how it is implemented, and why does the
documentation suggest that I even *might* be interested in something that is a mere
implementation detail, completely beyond my concern?
That's when I posted the request and went to bed...
On Thu, 31 Jul 2008 09:07:34 -0400, "Michael Phillips, Jr." < XXXX@XXXXX.COM >