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

2018-05-07 Thread Pali Rohár
On Wednesday 18 April 2018 15:45:20 Giuseppe Bilotta wrote: > On Wed, Apr 18, 2018 at 3:33 PM, Pali Rohár wrote: > > On Thursday 12 April 2018 16:34:15 Adam Jackson wrote: > >> This should print the RANDR data in a separate stanza after the main > >> output, like the other extensions do. Again: th

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

2018-04-18 Thread Giuseppe Bilotta
On Wed, Apr 18, 2018 at 3:33 PM, Pali Rohár wrote: > On Thursday 12 April 2018 16:34:15 Adam Jackson wrote: >> This should print the RANDR data in a separate stanza after the main >> output, like the other extensions do. Again: the purpose of the core of >> xdpyinfo is to tell you what the connect

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

2018-04-18 Thread Pali Rohár
On Thursday 12 April 2018 16:34:15 Adam Jackson wrote: > This should print the RANDR data in a separate stanza after the main > output, like the other extensions do. Again: the purpose of the core of > xdpyinfo is to tell you what the connection block says. Don't make it > print something else. Th

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

2018-04-12 Thread Adam Jackson
On Thu, 2018-04-12 at 20:47 +0200, Pali Rohár wrote: > XServer with enabled XRANDR 1.2 extension does not provide correct > dimensions from DisplayWidthMM() and DisplayHeightMM() calls anymore. > Values are calculated from fixed DPI 96. > > Therefore when XRANDR 1.2 extension is enabled, present a