W3C home > Mailing lists > Public > www-lib@w3.org > April to June 2001

RE: wwwlib eventloop setup.

From: <lucas@mach8.nl>
Date: Fri, 20 Apr 2001 13:49:19 -0400 (EDT)
To: www-lib@w3.org
Message-ID: <Pine.LNX.4.21.0104201936430.22314-100000@s034.widexs.nl>
Hi Fred, 

  Thanks for you reply. Excuse my ignorance on the topic, but I've got a
few questions below :

> 	originalappproc =
> (WNDPROC)SetWindowLong(GetWinHandle(main.Window),GWL_WNDPROC,(long)
> myAsyncWindowProc);

I think I get this. I 'steal' the server's WindowsProcedure, and replace
it with my own... I'll then pass on almost all messages back to the 'real'
windowsproc.

> 		if (!CallWindowProc(libwwwwinproc,hwnd,uMsg,wParam,lParam))
>     			return (DefWindowProc(hwnd, uMsg, wParam, lParam));

Where do I get this libwwwinproc? Is this the hook into libwww that I'm
lookingfor?... Am I correct to assume that lbwww runs on 'windowmessages'
and that it reacts on those, and does 'its stuff' ?

In this specific code example, you pass the messaage to what I believe to
be is the libraries windows procedure... If that does not handle it, it
should get passed to the servers window procedure right?..
The server's windowsproc we stored a while ago. Shouldn't the message go
to that instead of DefWindowProc() ?   I thought DefWindowProc will send
it to the default windowproc which in this case would be
myAsyncWindowProc().   Am I getting things backward now?

If the library's windows procedure does handle a message, should it not be
sent to the server'winproc anyway? (in case it depends on some messages
arriving to it, which in this scenerio I might keep from it?)

Thanks again for your answer, I really appriciate it.

Bye, Lucas
Received on Monday, 23 April 2001 04:17:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:39 GMT