>>>I'm just curious because of what Fred Taylor told me that VFP Native controls are not actual windowed controls but bitmap representations of windowed controls. Please refer to:
>>>Thread#1035003
>>>Message#1037110
>>>
>>>So I was wondering how the events are fired and the control message looping is handled?
>>>
>>
>>
>>Hi Dawa,
>>
>>Just a thought. At first, all windows messages is actually handled by the form (or the topmost control that is an actual window control). Then VFP altered the message to decide what to do next. If you look at the SysTray sample from VFP, you will noticed there is a comments like this:
>>"MouseWheel event is the only VFP event that doesn't alter..."
>>
>>For instance, The MouseMove event is actually a WM_MOUSEMOVE that is received on VFP form. Then the form looked further if there is any VFP control underneath. If there is a control then VFP will process the next step, and so on.
>>
>>About how VFP drawing/render the control itself I have no idea <*g*>. But if you want to know how to draw something on the window, read GDI/GDI+ documentation at MSDN.
>>
>>To see whether VFP control is a window control or not, you can use SPY++, WinSpy, or you can download my WinTracker on UT download area (file #27704)
>>
>>Again, that's purely just a thought! :-)
>>
>>Regards
>
>
>Thanks Herman! I use Spy++. I'll check out your download too.


You're welcome. One more thing about part of the drawing. Apparently, VFP using "OwnerDrawn Techique" for the controls as mentioned here:

http://blogs.msdn.com/calvin_hsia/archive/2004/09/10/228001.aspx

Regards