Hi,
On 11/15/2011 01:38 PM, Uli Schlachter wrote:
awesome handles appearing and disappearing screens quite poorly. Whenever it
receives a RandrScreenChangeNotify event, it restarts. Since Xinerama doesn't
support dynamic screen configuration, awesome
has to ignore any changes if the server doe
I'm afraid I cannot help you further, because my experience is limited
to system running open drivers, which seems to behave totally
different - especially it still reports the monitor as connected even
if it is switched off and has more clear reports on Xinerama (in your
list of extensions it is l
On 11/15/2011 04:53 PM, Paweł Rumian wrote:
>> I use gentoo with -xinerama useflag :) So xdpyinfo says "XINERAMA
>> extension not supported by xdpyinfo".
>
> Strange, because on my gentoo box with USE='-xinerama' I have:
>
> $ xdpyinfo -ext XINERAMA | tail -n 5
I ran it and i get this:
http://
> I use gentoo with -xinerama useflag :) So xdpyinfo says "XINERAMA
> extension not supported by xdpyinfo".
Strange, because on my gentoo box with USE='-xinerama' I have:
$ xdpyinfo -ext XINERAMA | tail -n 5
XINERAMA version 1.1 opcode: 150
head #0: 1280x1024 @ 2960,0
head #1: 1280x1024 @ 0,
On 11/15/2011 04:20 PM, Uli Schlachter wrote:
I bet that the following command will confirm that Xinerama is
enabled:
$ xdpyinfo -ext XINERAMA | tail -n 10
I use gentoo with -xinerama useflag :) So xdpyinfo says "XINERAMA
extension not supported by xdpyinfo".
But i will recompile it with +xine
On 15.11.2011 13:43, andreas wrote:
> On 11/15/2011 01:38 PM, Uli Schlachter wrote:
>> BTW: You *are* using Xinerama. That's how multi-head works in X11 (as long as
>> you want to be able to move windows between screens, without that feature you
>> can disable Xinerama and use protocol screens).
>
On 11/15/2011 01:38 PM, Uli Schlachter wrote:
BTW: You *are* using Xinerama. That's how multi-head works in X11 (as long as
you want to be able to move windows between screens, without that feature you
can disable Xinerama and use protocol screens).
Xinerama would result in lower performance an
2011/11/15 andreas :
> On 11/15/2011 01:00 PM, Paweł Rumian wrote:
>>
>> I suppose (but probably Uli, Julien or anxrc will be able to clarify
>> it) that awesome takes info about monitors straight from RandR. You
>> can check that even after the monitor is switched off, 'xrandr -q'
>> still reports
On 15.11.2011 10:52, andreas wrote:
Hi,
i want to know how awesome manages Monitors when they are disconnected
and connect. My scenario is the following.
I have three LCD Monitors on my workstation. I use a AMD/ATI Radeon 5770
with 5 mini Displayports to which 3 HP ZR24W are connected via DP.
I
On Tue, Nov 15 2011, andreas wrote:
> What does awesome to prevent the issue i have with i3? Awesome acts
> exactly how i need it. I turn off all my 3 LCDs when i leave my place
> and when i return i turn them on and want everything on the places and
> screens they had before i left. But how does
hello,
I suppose (but probably Uli, Julien or anxrc will be able to clarify
it) that awesome takes info about monitors straight from RandR.
You can check that even after the monitor is switched off, 'xrandr -q'
still reports it as connected. I don't know how i3 handles that.
As for the driver - f
Hi,
i want to know how awesome manages Monitors when they are disconnected
and connect. My scenario is the following.
I have three LCD Monitors on my workstation. I use a AMD/ATI Radeon 5770
with 5 mini Displayports to which 3 HP ZR24W are connected via DP.
I also use the proprietary driver fglr
12 matches
Mail list logo
