Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Overhead when using BINDEVENT and CallWindowsProc
Message
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Miscellaneous
Thread ID:
01182389
Message ID:
01184074
Views:
21
Thanks Anatoliy - love the hat - I will cruise your links!

I have been messing with the WM_SIZING message (START (WM_ENTERSIZEMOVE), resize in progress (WM_SIZING) and resize end (WM_EXITSIZEMOVE) and it's for real. I was expecting a series of starts and stops like the form's resize - but it behaves as hoped - when the button goes down on the edge of the form - there is "1" start message - then a bunch of in progress messages - until I let the mouse up and then the "stop sizing" message.

What an amazing feature.

Now I am wondering how I can hook a BINDEVENT to monitor "activities" in the OS (XP) PORTs collection.

The BINDEVENT / Windows Messaging "feature" is nothing short of amazing. I am fantasizing - thinking about all the thngs that we can now do with a COM. I think we can do anything now. It's really Amazing - I could eat up a year with that feature and still not explore every opertunity it may present - thanks for the links.


>Terry,
>
>Take a look at these code samples:
>
>How to hot-track menu item selection in top-level form (requires VFP9)
>http://www.news2news.com/vfp/?example=521
>
>Placing a button on the VFP form as a new child window
>http://www.news2news.com/vfp/?example=274
>
>Dragging files from Explorer window and dropping them on FoxPro control (requires VFP9)
>http://www.news2news.com/vfp/?example=323
>
>They all use BINDEVENT in combination with GetWindowLong, WindowProc and CallWindowProc API calls.
Imagination is more important than knowledge
Previous
Reply
Map
View

Click here to load this message in the networking platform