Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
VFPx+Ctl32+CodeBook Declare DLL error in exe not VFP IDE
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Fonctions Windows API
Versions des environnements
Visual FoxPro:
VFP 9 SP1
OS:
Windows 2000 SP4
Database:
Firebird
Application:
Desktop
Divers
Thread ID:
01365915
Message ID:
01366594
Vues:
22
>> Is it safe to always make a call to ...Long() everytime a call needs to be made to ...Proc()?
>
>I think this is safe. But the better way is to call it only once per each HWnd value, and then use the result every time that HWnd is submitted to the CallWindowProc.
>
>Normally the address for the window procedure for a given HWnd does not change unless you hook it directly, for example by calling the BINDEVENT() or calling the SetWindowLong().

Okay, thanks a lot. I can check it against a new storedHWnd property, if it differs than the previous number I can get a new ...Long() and then submit to the ...Proc() call.
Regards
Bhavbhuti
___________________________________________
Softwares for Indian Businesses at:
http://venussoftop.tripod.com
___________________________________________
venussoftop@gmail.com
___________________________________________
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform