[rox-users] ROX-Filer 2.1.2 skipping to the left with xinerama

[Kacper W. <ka...@on...>]

Hi all,
I'm a zeroinstall user, and I have a two-head Xinerama setup. Recently, =20
ROX-Filer has been insisting on staying on my left screen; one can move =20
it onto the right screen, but as soon as one enters another directory, =20
the filer window will reposition itself onto the left screen. This =20
happens regardless of whether the left screen is xinerama screen 1 or =20
0, so I suspect it has something to do with rox requesting to be near =20
0,0 (top left).

A friend of mine, with a similar setup, has the same problem, -unless-=20
he turns on "merged framebuffer mode" and pseudo-xinerama extentions =20
*off* in his proprietary nvidia X drivers.

We have spent many hours hunting down the cause of the problem, as it =20
is very annoying, and we have found that rox 2.1.1 and below are not =20
affected with the problem. Rather, rox 2.1.2 is where the problem was =20
introduced. I've had a quick look at the changelog, and I do not see =20
anything in there that could cause the problems, unless it's this:

08-Apr-2004
~~~~~~~~~~~
Added Xinerama support (Tony Houghton).

Although I was under the impression that this "Xinerama support" was =20
only the added feature of confining the panel(s) to one xinerama =20
screen. Indeed, turning this option on or off does not fix the problem =20
we're having currently.

I would appreciate it greatly if you:

1) could tell me how to get 0install ROX-Session to use v2.1.1 of the =20
filer instead of the latest one?

2) had any pointers for how to permanently fix this problem, ie by =20
pointing at specific lines of code.

3) knew whether there are any plans to add support for different panels =20
confined to different monitors, ie creating essentialy Z =3D (4 x number-=
=20
of-screens) panel edges.

TIA
-Kacper