Hi Alex,
On Mon, 17 Sep 2001, Alexander R Angas wrote:
> >From what I've seen, it's whenever there is a message waiting. If we are
> going to write our own message loop however, I will implement that in my
> test app and make sure. So I'll get back to you on that one. (a)
>
> By the way, when I say message loop, I mean something like this running as
> the server (stolen from Platform SDK, Aug 2001 docs):
>
> // Start the message loop.
>
> while( (bRet = GetMessage( &msg, NULL, 0, 0 )) != 0)
> {
> if (bRet == -1)
> {
> // handle the error and possibly exit
> }
> else
> {
> TranslateMessage(&msg);
> DispatchMessage(&msg);
> }
> }
>
> Looking at that above, I would say that DispatchMessage is what causes the
> message to be processed (see (a) above).
Excellent- now we're getting somewhere! What does TranslateMessag() do?
What do the other parameters go GetEvent() mean? Is it possible to specify
a timeout there?
[...]
[Docs]
> > It is missing:
> > 1. Documentation for the sound subsystem
> > 2. 80% of the gfx subsystem documentation that _should_ be there
> > 3. Our platform-independant tools.c functionality
> > 4. A short introduction to the core header files and some information that
> > maps functionality to C files
>
> > I think doing 3 and 4 would be most important. 1 might be about to change
> > somewhat anyway, while 2 is of little interest to most people
> > (apparently) and would require a lot of work to be finished.
>
> Yes I think you're right with those probabilities, but it's a shame that gfx
> can't be better documented. Especially if we ever want to get DirectDraw
> working on Win32 (and that code itself is largely undocumented).
The following is documented already:
- The complete gfx driver API (gfx_driver.h) (READ IT if you want to work
on gfx drivers)
- Data structures and global static inline functions and some #defines
that may be helpful for gfx drivers (gfx_system.h)
The only things missing are some auxiliary functions for use by gfx
drivers.
The gfx subsystem is relatively large to allow some flexibility in gfx
drivers, and the layers it is built from and how they interact would've
made up most of that documentation. It would have been of little interest
to driver writers.
llap,
Christoph
