--- In [email protected], "Sheri" <[EMAIL PROTECTED]> wrote: > > I don't think win.getrect(bname) (or win.left, win.top, win.right > or win.bottom, each of which return values consistent with > win.getrect) is returning the true location of a bar. If, after > importing the ini (where properties position the bar as > RightCaption with offsets), I use win.mouseto(win.right(bname), > win.bottom(bname)) the mouse pointer goes near the center of the > window instead of near the lower right edge of the bname bar.
In fact the win plugin services find the bar at left:546 top:502 right:757 bottom:521 whereas other windows utilities like winspector see it at left: 825 top: 148 right: 1036 bottom: 167 The width and height which compute from the win plugin's coordinates are correct but the position is wrong; the X-coordinates are too low by 279 and the Y-coordinates are too high by 354. If I maximize the active window where bname is initially displayed near the rightcaption and retest getting the bar's coordinates, the bar loads higher on the screen but the win plugin still reports: left:546 top:502 right:757 bottom:521 This increases the variance e.g., the initial position per winspector becomes: left: 937 top: 33 right: 1148 bottom: 52 Any alternative methods that would allow the script to get the bar's true screen coordinates? I've confirmed that If I provide the winspector identified coordinates with cl.addproperties for Left:, Top:, etc., the bar behaves correctly when converted to a floating bar . At least when followed by cl.refresh(bname). Regards, Sheri
