Comment 5 for bug 376848

Dear Johannes

Exuse my late answer.

Reading your recent posts I have to say that we both have the same approach.

First I want to say, that a Dual-Screen user doesn't need information
twice. Any 'clone'-behaviour or else is definitly not needed in your
desktop-cover-plugin.

On the other hand I would make use of the default window positioning
behaviour of exaile. Exaile is one of these programs that saves its
current position, when it is closed. It will reopen exactly at the
same place. Isn't that what we want with the desktop-cover-plugin?

I would do a plugin properties dialog wich gives the user the
possibility to change size of the plugin image.
Then there should be a preview button wich pops up a test image with
'ALT-LEFTMOUSEBUTTON' or so written on it.
The user could then drag the window to the position he wants.
There would be a 'save' button in the properties dialog too. Clicking
on it would save the given window position.
The user could then maybe have the option to fix the window all the
time at given position.
Otherways, he could always drag the window with Alt+Mouse. A dual
screen user could just drag the image on the other screen, if he
wanted.

The only thing that you would have to do, is to implement the
'save-current-position- feature in your plugin.

Wouldn't that be a nice 'gnome'-way to solve our little problem?

Greets

Martin

2009/5/22 Johannes Sasongko <email address hidden>:
> (BTW, I meant never mind about the script, not about the questions :-P .
> Sorry, had the page open for a few days and forget to reload.)
>
> For my own note: In a standard multiple-monitor setup, there is one
> screen spanning multiple monitors. Not sure how this plays with
> geometries/gravities, since I don't think there's a way to send a
> window to a specific *monitor*. Probably the most reliable way is to
> move the window manually and do away with the whole geometry/gravity
> thing.
>
> --
> 0.3: Desktop Cover Plugin changes screen on dual screen setup
> https://bugs.launchpad.net/bugs/376848
> You received this bug notification because you are a direct subscriber
> of the bug.
>