Hi,

First of all thanks for you fast reply.

On Mon, Dec 17, 2007 at 11:14:11PM +0100, Bart Samwel wrote:
> Hi Csillag,
>
> Csillag Tamas wrote:
>> I think I have an idea what to include in ibm-videobtn:
>> -action=/bin/true
>> +action=xrandr --auto
>
> Just checking, does it work if you replace it by
>
> action=/etc/acpi/videobtn.sh
>
> ? This is what all other video buttons do, and I am of course hoping that 
> we can consolidate this. :-)

Well it does not work. In fact it calls acpi_fakekey, which usally means
(as far as I know): let 'hald' handle the event which is not bad, but
nothing happens.

>> However this does not best way to do it, but it works and maybe it is
>> better than /bin/true.
>> This will only switch on the second display if is already connected, it
>> won't switch off unless disconnected.
>> Some further ideas:
>> Make an external script which toggles between:
>> switch off VGA: xrandr --output VGA --off
>> switch off internal display: xrandr --output LVDS --off
>> Detect if a xrandr aware video card is present (works with intel, not
>> sure about the others).
>> I think "xrandr --auto" is simple and safe enought.
>
> If this is needed, I think the "switch explicitly" option is probably 
> better, because I can think of some real use cases where you don't want to 
> disconnect the external monitor but you _do_ want to keep your display to 
> yourself. For instance, if you have a TV that automatically switches to a 
> certain input if it detects a signal (mine does that). Or if you're 
> preparing for a presentation, you might want to connect and test the output 
> and then switch back to only the internal display until you've finished 
> preparing.

I agree.

> Furthermore, if you want xrandr --auto, you really make users 
> expect real autodetection, which we can't do.

What do you mean by "real autodetection"?

> Better to keep it with the usual behaviour for these kinds of buttons.
> :-)

I agree with you. But I considered the "/bin/true" vs. "xrandr --auto"
scenario.

>> If someone have the resources to write the external script, the better.
>
> I'd definitely move this to an external script. Not much resources 
> required, but testing would be nice if it's implemented. If you would like 
> to help, I'd much appreciate it.

Time is the resource I do not have right now. I will get back to you in
January. I will ask the guys at linux-thinkpad mailing list how they do
and how it should be done.

Thanks.

Regards,
  cstamas
-- 
CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to