Export to GitHub

rainmeter - issue #61

Object Position Issues on Multiple Monitor Displays


Posted on May 18, 2009 by Massive Rabbit

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.

Comment #1

Posted on May 19, 2009 by Massive Monkey

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.

Comment #2

Posted on May 19, 2009 by Happy Cat

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.

Comment #3

Posted on May 20, 2009 by Massive Monkey

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

Comment #4

Posted on Dec 31, 2009 by Quick Rhino

(No comment was entered for this change.)

Comment #5

Posted on Jan 29, 2010 by Helpful Camel

Fixed. (r313, r317)

Status: Fixed

Labels:
Type-Defect Priority-Medium