X-1.0rc3: secondary monitor: Match.left/right/below doesn't work on secondary monitor --- workaround --- fixed 1.1.0 (2015-05-15+)

[Cristi Mihai]

***** workaround

only matches are affected. Region work.

cast matches to Regions:

s = Screen(1)
r = Region(s.find("asset.png"))
r.highlight()

---------------------------------------------------

App: Version X-1.0rc2 for Mac

Requirements: multiple monitor, with secondary monitor on the left (so Region coordinates are negative)

Use a script similar to this:

s = Screen(1)
r = s.find("asset.png")
r.highlight()

r.right(50).highlight() # is wrong

#probably there is a bug in computing the edge of the screen when the coordinates are negative.

Note: I haven't tried to move the secondary monitor on the right of primary to see if that still causes the issue.

[Cristi Mihai (cristi-mihai)]

I tested with other display arrangements, the computation of right() and left() fail on all the possible arrangements, so it's not dependant to the arrangement.

[RaiMan (raimund-hocke)]

Mac Lion confirmed.

For right() and left() the width of the new region is calculated using the width of the base region and not using the given width. This leads to the same negative value, no matter what value is given with left/right.

[RaiMan (raimund-hocke)]

below() seems to be wrong too.

Only Match objects have this effect.

Calculated Regions work ok.

Workaround: cast matches to Regions:

r = Region(s.find(image))
r.highlight(2)