Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On Monday 08 May 2017 09:55:08 Eric Anholt wrote: > That would also not be accepted. You don't get to rewrite output like > this in old CLI tools that have had consistent behavior for decades. It > causes breakage for systems expecting old behavior, even when that > behavior is unfortunate and

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

Pali Rohár writes: > [ Unknown signature status ] > On Saturday 06 May 2017 13:28:17 Julien Cristau wrote: >> On Fri, May 5, 2017 at 10:08:14 +0200, Pali Rohár wrote: >> > PING. >> > >> > I would like to know if there is some problem with this and >> > something needs to

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On Saturday 06 May 2017 13:28:17 Julien Cristau wrote: > On Fri, May 5, 2017 at 10:08:14 +0200, Pali Rohár wrote: > > PING. > > > > I would like to know if there is some problem with this and > > something needs to be reworked or if it can be accepted. > > > > Currently xdpyinfo report bogus

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On Fri, May 5, 2017 at 10:08:14 +0200, Pali Rohár wrote: > PING. > > I would like to know if there is some problem with this and something > needs to be reworked or if it can be accepted. > > Currently xdpyinfo report bogus dimensions and resolution values and lot > of people complain about

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

PING. I would like to know if there is some problem with this and something needs to be reworked or if it can be accepted. Currently xdpyinfo report bogus dimensions and resolution values and lot of people complain about this problem. It should be fixed. On Wednesday 12 April 2017 18:29:19 Pali

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On Thursday 13 April 2017 12:58:52 Michel Dänzer wrote: > On 13/04/17 12:52 PM, Keith Packard wrote: > > Pali Rohár writes: > > > >> Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense > >> for multi-monitor configuration. In most cases DPI is set to

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On Wednesday 12 April 2017 21:52:46 Keith Packard wrote: > Pali Rohár writes: > > > Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense > > for multi-monitor configuration. In most cases DPI is set to 96 as there is > > no sane value. > > > > Instead

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

On 13/04/17 12:52 PM, Keith Packard wrote: > Pali Rohár writes: > >> Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense >> for multi-monitor configuration. In most cases DPI is set to 96 as there is >> no sane value. >> >> Instead when XRANDR 1.2

Re: [PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

Pali Rohár writes: > Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense > for multi-monitor configuration. In most cases DPI is set to 96 as there is > no sane value. > > Instead when XRANDR 1.2 extension is supported, report dimensions and >

[PATCH app/xdpyinfo] Use XRANDR 1.2 extension for reporting dimensions and resolution per output

Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense for multi-monitor configuration. In most cases DPI is set to 96 as there is no sane value. Instead when XRANDR 1.2 extension is supported, report dimensions and resolution information per XRANDR monitor output. It should