Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Capture Windows Messages sent from a API to VFP. HELP!
Message
De
20/01/2001 03:58:45
 
 
À
20/01/2001 02:16:45
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Divers
Thread ID:
00466118
Message ID:
00466128
Vues:
15
>Need a Guru to help me with the following; will PAY if needed!
>My name is Gary I am a programmer in Fox but I am limited in some of the
>newer functions and abilities of VFP... I am looking for a way to
>caputre/hook into the Windows Messaging System so I can display the messages
>that are being sent to a defined window on the screen. There is a way to do
>this in basic (I'm not a basic programmer) but here is the we page
>http://support.microsoft.com/support/kb/articles/Q168/7/95.asp. Windows
>sends messages to each of your defined windows telling them how offten to refresh,colors etc.. A API that I'm working with sends a message to the VFP open window and I don't know how to capture it. Here is what the API vendor told me:

You're going to need to write code in either VB or C to hook the Windows event loop for these two messages as a part of an ActiveX control, and have them generate events that you can then hook with VFP code using VFPCOM, or write an FLL to tie C code directly to VFP. I believe there may be an example of such written by Christof Lange three or fours years ago; if you don't know C and are familiar with VB, creating a VB ActiveX control is probablyu easier, and some of the techniques you need are cover in Dan Appleman's first book on the Win32API and VB, available in many bookstores, or through sources like amazon or barnesandnoble

>
>************
>The following are two Windows messages sent by our API to the applicaton
>Window.
>
>WM_UPSDISCONNECT (defined as WM_USER+1)
>WM_UPSLINK (defined as WM_USER+2)
>
>Both of these messages use a UPSmsg structure to send message specific data.
>UPSmsg is defined as follows.
>
>typedef struct
>{
>long Statur;
>long StatusDesc;
>char szMsg[32];
>)UPSmsg;
>
>**************
>
>I also opend up a header file for basic which was sent as a sample for
>various API calls to find any info relating to the above; here is what I
>found: Note this is for BASIC
>
>' UPSlink-specific messages sent to the application window
>Public Const WM_USER = &H0400 ' defined by Windows
>Public Const WM_UPSCONNECT = WM_USER+1
>Public Const WM_UPSLINK = WM_USER+2
>
>
>If you think you could help or refer me to some GURU it would be
>appreciated.
>
>Gary Mathis
>Carrera Computers
>
>Ph: (909) 678-4522
>fax: (909) 678-3483
>email: gary@frtplus.com
EMail: EdR@edrauh.com
"See, the sun is going down..."
"No, the horizon is moving up!"
- Firesign Theater


NT and Win2K FAQ .. cWashington WSH/ADSI/WMI site
MS WSH site ........... WSH FAQ Site
Wrox Press .............. Win32 Scripting Journal
eSolutions Services, LLC

The Surgeon General has determined that prolonged exposure to the Windows Script Host may be addictive to laboratory mice and codemonkeys
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform