Object Position Issues on Multiple Monitor Displays

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install Rainmeter on a multiple monitor display with secondary monitors
in the negative coordinate direction in respect to the primary monitor.
2. Place objects on the negatively coordinated display.
3. Refresh.

What is the expected output? What do you see instead?
The objects should remain on the secondary monitor. However, they move to
the left edge of the primary monitor.

What version of the product are you using? On what operating system?
Rainmeter 0.14.1 on Windows 7

Please provide any additional information below. If the problem is a
related to some config option attaching a example is always a good idea.
Try to keep it as simple as possible and make sure that it is a fully
working Rainmeter config (i.e. it includes all graphics too).
This occurs on all configs.

Original issue reported on code.google.com by teaKni...@gmail.com on 18 May 2009 at 8:45

[GoogleCodeExporter]

You must use the latest untested versions of Rainmeter, to be able to set which
monitor a skin stays on. If you have installed the latest, open your 
rainmeter.ini
and after the x position of the meter you want on the second desktop add @2
representing the second monitor.

For future help could you please direct questions, bug reports, and ideas to
http://www.rainmeter.net/forum/index.php , we are trying to keep the developers 
from
having to spend any extra time reading posts here, that we users may be able to 
resolve.

Original comment by JMHarris...@gmail.com on 19 May 2009 at 2:42

[GoogleCodeExporter]

this is still an issue, as the expected action is that a config will stay in 
position
after a refresh, no matter where it is... this issue affects all multiple 
display setups.

there should be a check for which display "owns" a config, that automatically 
changes
the @2/@1 value when the skin is dragged to a different screen...

in the latest version, on xp, it took me a couple days to figure out what was 
going
on with my secondary display.

Original comment by gscho...@gmail.com on 19 May 2009 at 8:43

[GoogleCodeExporter]

Agreed, it should automatically add the @n. It does work if you add it manually
doesn't it?

Original comment by JMHarris...@gmail.com on 20 May 2009 at 3:06

[GoogleCodeExporter]

Original comment by kenz0.sa...@gmail.com on 31 Dec 2009 at 12:50

• Changed state: Accepted

[GoogleCodeExporter]

Fixed. (r313, r317)

Original comment by spx268 on 29 Jan 2010 at 12:06

• Changed state: Fixed