ASM Community

Cenox,

I am not completely sure of what you are after but be aware that while a MessageBox is running, the code in your own calling EXE is not running as a MessageBox is a small dialog that is run by the operating system that you cannot get at while it is running.

Try and explain a little more of what you are trying to do and I may be able to help you with it.

Regards,

hutch@movsd.com

Ok..

by the way i think i should have posted it into the main board :( .

another longer explanation for my prolly lil problem:

// Ive set a Timer:

.CONST

T_ID equ 1
T_INT equ 80

.CODE

[...]

.IF uMsg == WM_CREATE

Invoke SetTimer, hWnd, T_ID, T_INT, NULL

[...]


// I have set the Timer to check if a specific key has been pressed.
// So another important part:

.ELSEIF uMsg == WM_TIMER

Invoke GetAsyncKeyState, VK_F1
cmp eax, 0
je @F
Invoke Trn, oh, ADDR nh, 3, NULL
@@:
Invoke GetAsyncKeyState, VK_F2
cmp eax, 0
je @F
Invoke FindWindow, offset clsName, NULL
push eax
pop windhand
cmp al, FALSE
jnz @F
Invoke GetWindowThreadProcessId, windhand, addr pid
Invoke OpenProcess, PROCESS_ALL_ACCESS, NULL, pid
push eax
pop phandle
Invoke ReadProcessMemory, phandle, rs, addr buffer, 1, NULL
Invoke TrnEng, os, ADDR buffer, 1, NULL
@@:
Invoke GetAsyncKeyState, VK_F3
cmp eax, 0
je @F
Invoke Trn, oh, ADDR oh, 3, NULL
@@:

[...]

// So Far: A Timer is Set. If a specific Key (F1,F2,F3) got pressed another procedure gets started (Trn).
// @ F2 also some other Stuff.
// Ok a Part of Trn is:

Invoke FindWindow, offset clsName, NULL

push eax
pop windhand
cmp al, FALSE
jnz @F

Invoke MessageBox, hWndtr, offset err_run, offset cap_err, MB_OK+MB_TASKMODAL+MB_ICONWARNING
ret

[...]

// If the Window cant be found an error Msg gets opened.

Ok. The Problem now is that when i press several times F1 i get the same amount of MsgBoxes :).
So i want to stop the key check that the program only reacts again when the MsgBox has been closed.

One Method i described in my Post above is to set a "variabel" a.
a db 0
Then put around the MsgBox
inc a and dec a.

so befor the error window gets opened. it incs a and a gets 1. if the MsgBox is closed it gets 0 again.

AND IN the WM_TIMER i set .IF a == 0 [ the stuff above ] .ENDIF. I thougt that when the MsgBox is opened a gets 1 and thats why the part where it checks for key presses gets ignored and so no other MsgBox will popup until i close the MsgBox.


ACTUALLY no other MsgBox pops up when i press again F1 or F2,F3 when one is open. BUT after i close that one and i pressed one or more times one of the keys (f1..) the same MsgBox gets opened immediately after i close the one.
Also when the MsgBox is opened and i press some key (a,b,c,4,...) i hear a sound. But when i press f1,f2,f3 i dont hear that ;)...

I also tried it with a Killtimer before the MsgBox and the StartTimer after the MsgBox but then i get the same strange result as stated above ...

puuhh.. always the little problems are the big ones :D.

Ok...

Problem solved.

( Credits to f0dder who helped me and wrote the code )

A better way to handle these hotkeys is to see if the state of the hotkey is 'down' or 'up'.
If it is 'up' the hotkey was pressed.

For e.g. F1 we need to put the following code into WM_TIMER when a timer is set:

Invoke	GetAsyncKeyState, VK_F1			; F1 Pressed?

test	eax, 80000000h				; if most significant bit set, key is down

setz	al



; al == 0, meaning key was released. If old state is down, trigger action.

; al == 1, key is up. Go directly to "store"



cmp		al, 1

je		@@store

Invoke Trn, oh, ADDR nh, 3, NULL	;Start my Procedure

@@store:

mov		[isF1down], al

Dont forget to set "isF1down db 0" in your .DATA Section.

Then it is also workin to skip that Part when the MsgBox is open like i wrote it in my posts above!

Maybe it helps also somebody else sometime :).