ASM Community

Hey guys.

I have created a Proc that I use to subclass my edit controls on my dialog. Everything works great with it, only thing that I am trying to find out is - when the Proc takes over control, is there an initial message sent to the new Proc stating this? I want to do some initialization for the controls here. I want to add a text limit to the controls in this proc instead of getting the handle to each and every edit control in the WM_INITDIALOG and setting them there.

here is the proc

EditSubProc proc hWin:HWND,uMsg:UINT,wParam:WPARAM,lParam:LPARAM

mov eax, uMsg
.if eax==WM_LBUTTONDOWN
invoke CallWindowProc,OldEditWndProc,hWin,
uMsg,wParam,lParam
invoke SendMessage,hWin,EM_SETSEL,0,-1
ret

.endif
invoke CallWindowProc,OldEditWndProc,hWin,
uMsg,wParam,lParam

ret


EditSubProc endp


I was wondering after you use the SetWindowLong API function to re-associate this new Message Proc with the controls does the new Proc get a message stating this?

ie. like this,
WM_NEWPROCTAKINGOVER
....do some initialization here

I looked through all the docs I got and can't see anything, but maybe one of you guys worked with something like this before

thanx

Just another thought: is the subclass necessary? In my opinion you should be subclassing if you have no other means to modify a windows behaviour.

How about having an array of window handles and processing them in a loop:

if message == WM_INITDIALOG

for (i = 0; i < TEXT_CONTROLS; i++)
hwnd_array = createwindow, "edit", ....

And you can just process the EN_SETFOCUS in your dialog proc:

.if (message == WM_COMMAND && wParam == EN_SETFOCUS)

sendmessage, hwnd_array, EM_SETSEL, 0, -1

Dunno, just a thought :)