Closed maho closed 2 years ago
See also #16, which addresses this same issue, with a slightly different approach. I'm not sure which will perform better.
On 05/03/2013 04:59 PM, raztus wrote:
See also #16 https://github.com/wertarbyte/autorandr/issues/16, which addresses this same issue, with a slightly different approach. I'm not sure which will perform better.
I think my solution is better, but both are similar.
pozdrawiam
Łukasz Mach - lukasz.mach@pagema.net
I vote for this approach instead of #16. It is not always reasonable to turn off all displays first. On the other hand, it would be much faster to do all the turnoffs in a single command, then let a second command activate outputs.
On 03.07.2013 21:55, Helge wrote:
I vote for this approach instead of #16 https://github.com/wertarbyte/autorandr/issues/16. It is not always reasonable to turn off all displays first.
Note, that this approach also can turn off all displays first, depending on configuration.
EG, when you switch from LVDS+VGA to HDMI, or LVDS to VGA+HDMI. It will turn off LVDS first, next turn on VGA and HDMI.
However - it works ;)
pozdrawiam
Łukasz Mach - lukasz.mach@pagema.net
I made a pull request, #21, with a similar solution, but combining both the speed from #16 and correctness of this solution. It issues two xrandr commands to quickly disable then enable outputs, but instead of blindly disabling all connected outputs, it rearranges the configuration commands.
I believe this is outdated a bit.
I noticed that autorandr doesn't work when I'm connecting 2 external displays. Autorandr then called xrandr --output LVDS1 --off --output HDMI1 ... --output VGA1 ....., and xrandr refused to operate on three outputs simultaenously (I suspenct that intel driver can "see" only two outputs in one time).
So, I modified code to split options per output, execute "--off" options first, next "turn on" options next.