Odd WinActivate behavior?

[Ruevil2]

OK so I have run into what I think is a recent bug in WinActivate. I don't think it used to run this way.

Here is my code:

Code: Select all

F12::
	WinActivate, ahk_class RCLIENT
	WinGetPos,,, w, h, A
	MouseMove, (w*.10), (h*.05)
return

If the window I am targetting(RCLIENT) is the active window, the hotkey never activates AT ALL. Zero lines executed in code history and return continues to count. Now, if the window I am targetting is NOT the active window, the code executes fully and properly.

[Capn Odin]

Just to be clear you get this behaviour with just the supplied code, it is not taken out of a larger script ?

Since it sounds like the behaviour of #IfWinNotActive

[Ruevil2]

Just to be clear you get this behaviour with just the supplied code, it is not taken out of a larger script ?

Since it sounds like the behaviour of #IfWinNotActive

Yes I was able to recreate the bug with just the supplied code. Although the code came from a much larger script, it is contained within a
function and I do not use any directives in the script.


I will have to check my home computer now, as I can't seem to reproduce the effect on my work PC, even using the same script.

Could this strange behavior have been caused by a previous version of my script hanging or something?

[jeeswg]

Admin window? I think that would be consistent behaviour. 50% of the time problems are because it's an Admin window. (I didn't think of it, when I first read the problem description, only now.)

[Ruevil2]

I will have to check my home computer now, as I can't seem to reproduce the effect on my work PC, even using the same script.

Well I guess that was probably caused by maybe another program running or something because now I can't reproduce the problem. I'm using the same unchanged piece of test script for all testing. I have no idea. Gremlins...