| 1 |
On Monday 13 October 2008 13:53:49 YoYo siska wrote: |
| 2 |
> tabletka ~ # equery hasuse xinerama | wc -l |
| 3 |
> 285 |
| 4 |
> |
| 5 |
> most of them are apps from kde-base/* (3.5.9), seems that it changed |
| 6 |
> between 3.5.9 and 3.5.10, plus iwndow managers like fluxbox, openbox... |
| 7 |
|
| 8 |
That looks better. I was convinced that most kde-3 apps had a xinerama USE |
| 9 |
flag, hence my 'emerge -e world' comment that Iain picked up on. |
| 10 |
|
| 11 |
I wonder why it was changed for KDE-3.5.10, it seems that Xinerama support is |
| 12 |
now automatically built for most of KDE-3 (deduced by examining the ebuild |
| 13 |
and ldd output) |
| 14 |
|
| 15 |
> > Obviously, this understanding of mine is flawed. Which bit did I get |
| 16 |
> > wrong? |
| 17 |
> |
| 18 |
> Xinerama consists basically of two parts, the protocol to communicate the |
| 19 |
> position/sizes of screen between the Xserver and the applications (which |
| 20 |
> you usually get by enabling the xinerama use flag) and an xserver part |
| 21 |
> (module?) that you can use to set up the screens. What you said is |
| 22 |
> correct for the Xserver setup part... |
| 23 |
|
| 24 |
> You use either xinerama setup to put together completely different |
| 25 |
> displays (might be different cards, such as one nvidia, one ati, ...) |
| 26 |
> or twinview in case of a dualhead nvidia setup. But both this setups use |
| 27 |
> the xinerama protocol to let the apps/wm know the placement of the |
| 28 |
> monitors. |
| 29 |
|
| 30 |
<penny drops> |
| 31 |
|
| 32 |
OK, so there's a xinerama protocol and a xinerama lib and these are not the |
| 33 |
same thing |
| 34 |
|
| 35 |
</penny drops> |
| 36 |
|
| 37 |
-- |
| 38 |
alan dot mckinnon at gmail dot com |
Archives