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:
01182576
Views:
15
>My VFP 9 should be here in a few days. My main reason for the purchase was a project requires a "binding" to Windows Messaging functions.
>My project needs to bind to (at least) 3 CallWindowsProc "flags". I do not anticipated an "unbinding" to those events until the user closes the application.


The binding is done to Windows Messages for specified window or all windows. See http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_foxhelp9/html/e0aaf535-c606-44bd-b7c1-7d0341331d8f.asp and http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winui/winui/windowsuserinterface/windowing/messagesandmessagequeues/aboutmessagesandmessagequeues.asp


>How does messaging work? It seems every "message" will be caching through my event binder waiting for those 3 "particular" events to run a delegate>
>But I have not considered the "overhead"? Will a "start to end" binding to Window Messages affect the performance (speed) of my interface?


You specify in parameters to BINDEVENT() function wich Windows Message you're binding to
--sb--
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform