v25 BC break in WINDOW and ACTIVATE

Aug 23, 2010
589
7
v.25 introduced a new way to move or resize windows separately, that is breaking backward compatibility with existing scripts.
You can no longer move windows to -1 pixel off screen.
 
Aug 23, 2010
589
7
Because that's optimal position for the window I'm moving.
Change it to non-numeric value, "x" for example.
Then you would achieve the desired results without BC break.
 

rconn

Administrator
Staff member
May 14, 2008
11,931
133
-1 isn't necessarily off screen, it's just one pixel off the screen of one monitor. Dual monitor systems (depending on the configuration) will end up with a one-pixel stripe on one of the monitors.

Unless you're trying to hide one pixel of your window border on a single-monitor system, I don't see how this is of any benefit.
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
4,223
78
Albuquerque, NM
prospero.unm.edu
Because that's optimal position for the window I'm moving.
Change it to non-numeric value, "x" for example.
For a non-numeric do-nothing token, I'd suggest that a minus sign (sans digits) might be more intuitive. But if you really want to use a numeric value, -32000 is a lot less likely to intersect an actual monitor.
 
Aug 23, 2010
589
7
Why do you assume that the window I'm moving will inevitable end up on both monitors of the multimonitor system? Can't I move it to the side of one of the monitors, that isn't adjacent to another one????
(And yes, I have two monitors. And yes, I'm moving the window to the left side of the left monitor. And no, it's my choice where I want my windows. And it's only mine.)
 
Aug 23, 2010
589
7
For a non-numeric do-nothing token, I'd suggest that a minus sign (sans digits) might be more intuitive.
That could be.

Or just let /POS: accept either 4 or 2 numbers, and introduce a new switch "/SIZE:w,h".

P.S.
I don't recall if I mentioned it earlier, but there's a discrepancy between @WINPOS's "top,left,bottom,right" and
"/POS=left,top,width,height".
 
Aug 23, 2010
589
7
No, in this case, it was just a highlight.
At most, it would be useful to explicitly mention this caveat in the documentation, so people are aware.