Inconsistent @WINPOS // ACTIVATE /POS= behavior

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
Aug 23, 2010
85
1
#1
Aside from @WINPOS returning Y1,X1,Y2,X2, whereas ACTIVATE /POS= requiring X,Y,W,H, which can't be fixed without breaking backwards compatibility; there's one more inconsistency that should be attended:
Where @WINPOS returning values relative to the screen viewport, ACTIVATE /POS= operates relative to the desktop area. Which, in turn, results in the behavior similar to this:
Code:
ECHO %@WINPOS[=1396]
-4,18,724,1202
ACTIVATE =1396 /POS=18,-4,1184,728
ECHO %@WINPOS[=1396]
-4,40,724,1224