Was anybody here able to find a solution for this error? If so, please share - there seem to be quite a few people with this problem (myself included!). Thanks for any help!
I know I'm being lazy here and I should trawl the header files for myself, but what are the actual types for LPARAM and WPARAM parameters? Are they pointers, or four byte ints? I'm doing some C# interop code and want to be sure I get it working on x64 systems.
Mark HeathMark Heath5 Answers
LPARAM is a typedef for LONG_PTR which is a long (signed 32-bit) on win32 and __int64 (signed 64-bit) on x86_64.
WPARAM is a typedef for UINT_PTR which is an unsigned int (unsigned 32-bit) on win32 and unsigned __int64 (unsigned 64-bit) on x86_64.
These typedefs go back to the 16-bit days. Originally, LPARAM was a long (signed 32-bit) and WPARAM was a WORD (unsigned 16-bit), hence the W and L. Due to the common practice of passing casted pointers as message parameters, WPARAM was expanded to 32 bits on Win32, and both LPARAM and WPARAM were expanded to 64 bits on Win64.
In C#, you should use IntPtr for LPARAM and UIntPtr for WPARAM.
Note that despite the LP prefix, LPARAM is not a far pointer to an ARAM.
Lresult Callback Wndproc
LPARAM refers to a LONG_PTR and WPARAM refers to a UINT_PTR
On x86 they will be 4 bytes and on x64 they will be 8 bytes.
Wparam Win32
Brian R. BondyBrian R. BondyUpgrade Error Wparam 100 Lparam 1002 0
jpalecekWhat you need my friend is http://www.pinvoke.net/