Sorry to revive such an old topic, but has anyone found a work around to this?
I have tested the following with having my second monitor on the right side of the main and on top (with both having the same resolution).
$window(-1).dw/dh
returns 1920/1080
$mouse.dx/dy
returns x,y independent of monitor (x: 0 to 1920, y: 0 to 1080)
$window(-2).dx/dy
when mIRC is moved around on main monitor returns the following:
returns (x: 0 to 1920, y: 0 to 1080)
when mIRC is moved around on second monitor set to the right (side to side):
returns (x: 1920 to 3840, y: 0 to 1080)
when mIRC is moved around on second monitor set to the top:
returns (x: 0 to 1920, y: -1080 to 0)
one can move a window by command (/window) from monitor to monitor depending on the coordinates given.
example:
(depending on how you set up the monitors)
/window -d @test
; set window to (0,0) of second monitor when set to the top:
/window @test 0 -1080
; set window to (0,0) of second monitor when set to the right:
/window @test 1920 0
$window(@test).dx/dy
acts just like $mouse.dx/dy returning only a value from 0 to $window(-1).dw/dh
Tested on Windows 10 Home and mIRC 7.52
as the previous post mentions (CrashB) it is impossible to move a window round multiple monitors relying on $mouse.dx/dy
to me the best solution would be just to return values like $window(-2).dx/dy for $window(@name).dx/dy and $mouse.dx/dy