windowBoundingRect Bug

[WaltBrown]

Could someone post this in quality.runrev.com? I can't seem to get it to recognize me.

I have two screens, one above the other, with smaller primary below. I get this, regardless of the location of LC or my test stack on the two screens:

Code: Select all

windowBoundingRect: -121,160,1280,772
screenRect: 0,0,1280,800
screenRects: 0,0,1280,800
-224,-1050,1456,0
Stack rect: -224,-1031,1456,0 -- my test stack on secondary screen
Stack rect: 142,97,1100,719 -- my test stack on primary screen

The reason it's a bug is that I can't count on anything staying on just the secondary screen without scripting, which means I would have to modify LC code, not just my own. "windowBoundingRect" seems to use "screenRects" to calculate the X axis, but only "screenRect" for the Y axis, and when opening LC subwindows, some appear on the secondary screen (well-bahaved) and some appear on the primary (ill-behaved). This is also negatively affecting third party tools I have purchased.

I have tested this on Win Vista and Win 7, both x64.

Thanks,
Walt

Note that I searched quality.runrev.com and found a few related issues but none as specific as this.