On Wednesday 04 April 2018 16:00:39 Adam Jackson wrote: > On Wed, 2018-04-04 at 21:30 +0200, Giuseppe Bilotta wrote: > > On Wed, Apr 4, 2018 at 5:12 PM, Adam Jackson <a...@nwnk.net> wrote: > > > On Tue, 2018-04-03 at 22:15 +0200, Pali Rohár wrote: > > > > Gently reminder of this patch. Can you comment/review it? > > > > > > Nack. The whole point of (that part of) xdpyinfo is to show you what > > > was sent in the initial connection block. xrandr already exists, and > > > code exists that depends on xdpyinfo's output. > > > > Would it make sense to add the output from RANDR via an explicit `-ext > > RANDR` query similar to what is already done for XINERAMA, > > XInputExtension, etc? > > If it's going to be in xdpyinfo at all - and I kinda don't think it > needs to be, given xrandr already exists, but I don't insist on that - > then yes, it should be behind -ext RANDR. > > - ajax
The main problem is that majority of users use xdpyinfo for getting DPI of their monitors. And xdpyinfo reports totally bogus values. There are plenty of bugs and lot of reports about this problem. Really what is the purpose of reporting bogus values? -- Pali Rohár pali.ro...@gmail.com
signature.asc
Description: PGP signature
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
