Finally I get the code to you

vital at vital at
Mon May 1 23:39:18 EDT 2000

Does it has a need to validate if the message realy could be apply to the
asked widget? If so What would be done in case of bad message?

Vital Tremblay
vital at

At 21:37 00-05-01 -0700, you wrote:
>From the standpoint of the LCL here is what really occurs.
>When a program is started the application object gets created and and the
>initialize routing is called on the interface object. Here is where we tell
>the engine to create a engine instance. From then on the lcl will pass a
>message to the IntSendMessage routine telling the widget engine to do
>various things depending on what was passed. For instance the routine may
>get a message to create a form in that case lcl_win32_create_widget gets
>called and it internally creates a form. It will pass back a integer value
>"we'll call it the hwnd" which is the index of the component in the list.
>Inside of the interface object we set the LCL TComponent handle with that
>returned value because that is what we are going to use to access the
>instance. Now in the library you will need to do something like
>lcl_win32_reparent_widget(hwndparent, hwndchild: integer) and that will
>inturn set the parent of the child to the parent. Then you add something
>like lcl_win32_set_bounds(hwndwidget: integer;x,y,top,left: integer)  so
>internal you just grab that widget from the list and set the properties.
>Then you need to add a event hook I think I coded the stub into it but did
>not finish it. Something like lcl_win32_hook_mouse_move(hwndwidget: integer;
>fproc: pointer) You then assign a handler internal which will call this fpc
>method pointer. I know this sounds like a lot of stuff but it is pretty
>simple to implement.

More information about the Lazarus mailing list