Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFPx+Ctl32+CodeBook Declare DLL error in exe not VFP IDE
Message
General information
Forum:
Visual FoxPro
Category:
Windows API functions
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 2000 SP4
Database:
Firebird
Application:
Desktop
Miscellaneous
Thread ID:
01365915
Message ID:
01365957
Views:
20
All parameters look pretty normal from outside.

The first parameter is the address the original windows procedure. This is the most important parameter in this call. If it is invalid then the execution is passed to nowhere; and that may cause the exception. Usually the GetWindowLong is used to obtain it.

The second parameter is the handle of the window that receives the message.

Next parameter is the message itself -- 528 = 0x210 = WM_PARENTNOTIFY -- the parent window is notified when a child window either created (1) or destroyed (2).

Call 1: 4411862, 2034914, 528, 1, 1903924
means: parent window 2034914 is notified that the child window 1903924 is just created

Call 2: 4411862, 2034914, 528, 2, 1903924
means: parent window 2034914 is notified that the child window 1903924 is just destroyed

In both cases 4411862 is the address of the original windows procedure. Again, in my opinion, this is the only parameter where the things have chance to go wrong.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform