, no encryption/decryption...
Rémi
PS: Please add me to CC, I'm not subscribed to this list.
--
Pali Rohár
pali.ro...@gmail.com
___
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman
provide
correct DPI value.
Lot of users complains about incorrect DPI reported by xdpyinfo, see bug:
https://bugs.freedesktop.org/show_bug.cgi?id=23705
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
Without this patch `xdpyinfo | grep -A 4 ^screen` reports:
screen #0:
dime
On Wednesday 12 April 2017 21:52:46 Keith Packard wrote:
> Pali Rohár <pali.ro...@gmail.com> 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
> >
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 <pali.ro...@gmail.com> writes:
> >
> >> Current usage of DisplayWidthMM() and DisplayHeightMM() does not make sense
> >> for multi-monitor
On Sunday 28 May 2017 23:33:59 Pali Rohár wrote:
> Explicitly document and make it clear that those options does not change
> DPI of some monitor output. Also state that these options have no useful
> meaning for multi-monitor configuration.
>
> Signed-off-by: Pali Rohár <pa
Explicitly document and make it clear that those options do not change
DPI of some monitor output. Also state that these options have no useful
meaning for multi-monitor configuration.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
man/xrandr.man | 14 ++
1 file chang
On Saturday 10 June 2017 21:19:32 Pali Rohár wrote:
> On Sunday 28 May 2017 23:33:59 Pali Rohár wrote:
> > Explicitly document and make it clear that those options does not
> > change DPI of some monitor output. Also state that these options
> > have no useful mean
walter, any other objections? I fixed problematic parts which you pointed.
On Monday 24 July 2017 20:34:39 Pali Rohár wrote:
> Explicitly document and make it clear that those options do not change
> DPI of some monitor output. Also state that these options have no useful
> meaning
PING xorg-devel list.
Is something older needed to rework? If not, can you apply this patch?
On Monday 07 August 2017 18:45:22 walter harms wrote:
> Sorry, i had the idea you already got my ack.
>
> Reviewed-by: Walter Harms wha...@bfs.de
>
> Am 07.08.2017 12:56, schrieb Pali Ro
ect information is to query XRANDR.
--
Pali Rohár
pali.ro...@gmail.com
___
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
() calls to get correct
dimensions and resolution information.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
Changes since v1:
* Fixed detection of presence of XRANDR 1.2
* Fixed resolution calculation when dimensions are zero
---
Makefile.am |2 ++
configure.ac
Explicitly document and make it clear that those options does not change
DPI of some monitor output. Also state that these options have no useful
meaning for multi-monitor configuration.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
man/xrandr.man | 14 ++
1 file chang
Slash in previous documentation could be misunderstood as part of the
--dpi command line option. So fix it.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
man/xrandr.man |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/man/xrandr.man b/man/xrandr.man
On Sunday 28 May 2017 23:33:59 Pali Rohár wrote:
> Explicitly document and make it clear that those options does not
> change DPI of some monitor output. Also state that these options
> have no useful meaning for multi-monitor configuration.
I would like to remind this patch. Can y
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.
> >
&g
rmation per XRANDR monitor output. It should provide
> correct DPI value.
>
> Lot of users complains about incorrect DPI reported by xdpyinfo, see bug:
> https://bugs.freedesktop.org/show_bug.cgi?id=23705
>
> Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
> ---
>
Hi! I would like to remind this patch.
On Friday 18 August 2017 19:15:25 Pali Rohár wrote:
> PING xorg-devel list.
>
> Is something older needed to rework? If not, can you apply this patch?
>
> On Monday 07 August 2017 18:45:22 walter harms wrote:
> > Sorry, i had the id
12:56, schrieb Pali Rohár:
> > walter, any other objections? I fixed problematic parts which you pointed.
> >
> > On Monday 24 July 2017 20:34:39 Pali Rohár wrote:
> >> Explicitly document and make it clear that those options do not change
> >> DPI of some
On Wednesday 01 November 2017 21:04:17 Giuseppe Bilotta wrote:
> On Wed, Nov 1, 2017 at 11:25 AM, Pali Rohár <pali.ro...@gmail.com> wrote:
> > Hello, can somebody process this my patch?
> >
> > There are no objections for a long time and Walter already reviewed it.
>
or more than one monitor.)
>
> The primary monitor can change at runtime. The core DPI is only sent at
> initial connection. What would you like to do?
>
> Also: what's stopping us from fixing libXft instead?
But back to my documentation update patch. It is needed to rework it?
A
dimension does
not have to be correct and instruct user to run xdpyinfo with -ext RANDR.
Also update manual page and add information that xdpyinfo does not provide
correct information about DPI.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
Changes since v3:
* Always show core x screen
Hello, can you review my patch below?
On Thursday 12 April 2018 20:52:21 Pali Rohár wrote:
> Function strtod() sets strtod_error to the pointer of the first invalid
> character and therefore it does not have to be first character from input.
> When input is valid then it points to
On Wednesday 18 April 2018 15:45:20 Giuseppe Bilotta wrote:
> On Wed, Apr 18, 2018 at 3:33 PM, Pali Rohár <pali.ro...@gmail.com> 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
>
Hi! I would like to remind this patch which fixes dimensions values in
xdpyinfo output which are broken for many years...
On Tuesday 16 May 2017 22:04:57 Pali Rohár wrote:
> XServer with enabled XRANDR 1.2 extension does not provide correct
> dimensions from DisplayWidthMM() and DisplayHe
Explicitly document and make it clear that those options do not change
DPI of some monitor output. Also state that these options have no useful
meaning for multi-monitor configuration.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
man/xrandr.man | 19 +++
1 file c
On Wednesday 04 April 2018 11:12:53 Adam Jackson wrote:
> code exists that depends on xdpyinfo's output.
Exactly and that code expects that xdpyinfo provides correct output. But
it is broken since XServer for RandR 1.2+ capable screens started
reporting fixed values.
--
Pali Rohár
pali
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:
> > > > Ge
On Sunday 08 April 2018 19:22:28 Giuseppe Bilotta wrote:
> On Sun, Apr 8, 2018 at 4:33 PM, Pali Rohár <pali.ro...@gmail.com> wrote:
> > The main problem is that majority of users use xdpyinfo for getting DPI
> > of their monitors.
>
> And in the case of multiple monitor
On Wednesday 04 April 2018 13:59:15 Giuseppe Bilotta wrote:
> Hello,
>
> I took the liberty of moving the last paragraph of your email to the
> top because the reply I'm giving to that part covers both.
>
> On Wed, Apr 4, 2018 at 11:26 AM, Pali Rohár <pali.r
.
Update also error message about invalid argument.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
xrandr.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/xrandr.c b/xrandr.c
index 7f1e867..1960bbf 100644
--- a/xrandr.c
+++ b/xrandr.c
@@ -3115,9 +3115,10 @@ mai
RANDR.
Also update manual page and add information that xdpyinfo does not provide
correct information about DPI.
Signed-off-by: Pali Rohár <pali.ro...@gmail.com>
---
Changes since v2:
* Fixed dimensions calculation when rotation is active
* Show XRANDR output only when explicitly requested
*
ing and want.
--
Pali Rohár
pali.ro...@gmail.com
___
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
Gently reminder of this patch. Can you comment/review it?
On Tuesday 16 May 2017 22:04:57 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 fix
Hi!
On Wednesday 04 April 2018 09:47:59 Giuseppe Bilotta wrote:
> Hello Pali,
>
> I like the idea of this patch, wasn't aware of its existence, thanks
> for pinging me about it. A few comments below:
>
> On Tue, Apr 3, 2018 at 10:15 PM, Pali Rohár <pali.ro...@gmail.com>
On Monday 12 March 2018 09:19:57 Giuseppe Bilotta wrote:
> On Sat, Mar 10, 2018 at 4:23 PM, Pali Rohár <pali.ro...@gmail.com> wrote:
> > Explicitly document and make it clear that those options do not change
> > DPI of some monitor output. Also state that these options have
Hello, can you review 4th version of this patch below?
On Monday 07 May 2018 23:34:22 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 fix
Gentle reminder for a patch which I sent 5 months ago...
On Monday 07 May 2018 23:38:10 Pali Rohár wrote:
> Hello, can you review my patch below?
>
> On Thursday 12 April 2018 20:52:21 Pali Rohár wrote:
> > Function strtod() sets strtod_error to the pointer of the first invali
On Thursday 18 October 2018 09:03:27 Giuseppe Bilotta wrote:
> Hello,
>
> On Thu, Apr 12, 2018 at 8:53 PM Pali Rohár wrote:
> > - if (++i >= argc) argerr ("%s requires an argument\n",
> > argv[i-1]);
> > + if (++i >= argc || !argv[i
On Monday 26 November 2018 22:17:24 Pali Rohár wrote:
> Function strtod() sets strtod_error to the pointer of the first invalid
> character and therefore it does not have to be first character from input.
> When input is valid then it points to nul byte. Conversion error is
> indicat
On Sunday 30 December 2018 13:51:10 Walter Harms wrote:
>
>
> > Pali Rohár hat am 29. Dezember 2018 um 18:45
> > geschrieben:
> >
> >
> > On Monday 26 November 2018 22:17:24 Pali Rohár wrote:
> > > Function strtod() sets strtod_error to the
with trailing or leading whitespaces is invalid too.
Update also error message about invalid argument.
Signed-off-by: Pali Rohár
--
Changes since v1:
* Get same error message for `xrandr --dpi ''` and `xrandr --dpi ' '`
* Make the check for dpi <= 0
* Do not accept leading whitespaces (trailing w
On Sunday 30 December 2018 14:11:13 Pali Rohár wrote:
> On Sunday 30 December 2018 13:51:10 Walter Harms wrote:
> >
> >
> > > Pali Rohár hat am 29. Dezember 2018 um 18:45
> > > geschrieben:
> > >
> > >
> > > On Monday 26 November 20
On Wednesday 24 April 2019 16:29:25 Pali Rohár wrote:
> On Sunday 30 December 2018 14:11:13 Pali Rohár wrote:
> > On Sunday 30 December 2018 13:51:10 Walter Harms wrote:
> > >
> > >
> > > > Pali Rohár hat am 29. Dezember 2018 um 18:45
> > > >
43 matches
Mail list logo
