I have difficulties with parameters like :
WndProc proc hWnd:HWND, uMsg:UINT, wParam:WPARAM, lParam:LPARAM
Searchin windows.inc will reveal:
WPARAM TYPEDEF UINT
UINT TYPEDEF DWORD
So uMsg and wParam woul be declared as DWORD. Why not declaring them as wParam:DWORD?

How Do I treat wParam if I want to copy a key returned from the keyboard?
push wParam
pop wont do.

Any suggestions?

Thx, Klod
:stupid:
Posted on 2003-10-04 13:35:39 by Klod
About LPARAM WPARAM an such:

Maby it's becouse we want to feel yourselfes at home when we read MSDN

About second question:
I have a queston?. have you seen Iczelion's tutorials ??
Posted on 2003-10-04 14:06:48 by AceEmbler
1. To make C coders feel at comfortable
2. What is IDX? A constant or a variable? If it is a constant you can do the following:


mov eax, wparam
mov [buffer+idx], eax

If it is a variable, you are handling it the wrong way.
Posted on 2003-10-04 22:57:39 by roticv
I'm working on tutorial #6
In tutorial # 3
WndProc proc hWnd:HWND, uMsg:UINT, wParam:WPARAM, lParam:LPARAM
The first parameter, hWnd, is the window handle of the window that the message is destined for. uMsg is the message. Note that uMsg is not a MSG structure. . wParam and lParam are just extra parameters for use by some messages. Some messages do send accompanying data in addition to the message itself. Those data are passed to the window procedure by means of lParam and wParam.
This doesen't describe the difference between
wParam:DWORD
wParam:WPARAM

Since the keycode retrieved from wParam is stored in the low bite,
Data:
buffer db 0
Code:
mov edx, wParam
mov , dl
should work?

Masm32 does not agree with my intrepretation.
:grin: :o
Posted on 2003-10-04 23:09:35 by Klod
1. They are the same. No difference.
2. Usually variables are dword or an array of bytes. Your code should work by the way.
Posted on 2003-10-05 02:57:31 by roticv