i didnt preserve them. I just have to for example push them in the begining of my app and then pop them out while closing app ??
Posted on 2003-07-10 05:37:33 by AceEmbler
Generally just preserve the callback functions like wndproc and dlgproc. The rest of the functions can follow your own rules.
Posted on 2003-07-10 07:10:10 by roticv
is that so hard to type PUSHAD and POPAD? :grin: :grin: :grin:
Posted on 2003-07-10 13:38:21 by wizzra
AceEmbler,

It seems to work OK on Windows XP Professional SP1.

Charles
Posted on 2003-07-10 21:04:22 by cdquarles

is that so hard to type PUSHAD and POPAD? :grin: :grin: :grin:


When u dont know where. It is.

I added pushad when WM_CREATE and popad just before PostQuitMessage but my program just crashed.
Posted on 2003-07-11 18:08:56 by AceEmbler



When u dont know where. It is.

I added pushad when WM_CREATE and popad just before PostQuitMessage but my program just crashed.

Do you know what you are doing?
Posted on 2003-07-12 02:52:13 by roticv



When u dont know where. It is.

I added pushad when WM_CREATE and popad just before PostQuitMessage but my program just crashed.


Hi AceEmbler,

You only have to preserve 3 registers, and you do it in your WindowProc:
WindowProc PROC uses esi edi ebx hWin:DWORD,uMsg:DWORD,wParam:DWORD,lParam:DWORD


.IF uMsg == WM_CREATE

.
.
.
RET
WindowProc ENDP
When you use "uses" there is no need for pushes and pops, it is all handled by the assembler.
Posted on 2003-07-12 03:25:03 by donkey
thx donkey i forgot about this method :alright:
Posted on 2003-07-12 04:07:33 by AceEmbler