[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: x-display-pixel-width/height inconsistency

From: Dmitry Gutov
Subject: Re: x-display-pixel-width/height inconsistency
Date: Thu, 21 Mar 2013 06:43:28 +0400
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4

On 21.03.2013 5:51, YAMAMOTO Mitsuharu wrote:
First, thanks for many experiments.

No problem. Your latest patch has two typos:

w32fns.c: In function `Fx_display_mm_height':
w32fns.c:4737: error: `dc' undeclared (first use in this function)
w32fns.c:4737: error: (Each undeclared identifier is reported only once
w32fns.c:4737: error: for each function it appears in.)
w32fns.c: In function `Fx_display_mm_width':
w32fns.c:4755: error: `dc' undeclared (first use in this function)

With them fixed, the behavior seems to be right:

ELISP> (x-display-pixel-height)
ELISP> (x-display-pixel-width)
ELISP> (display-mm-height)
ELISP> (display-mm-width)

That's the correct values for the bounding box. At least, the first two.

I understand users want to know the size of each monitor rather than
the total size.  But that does not justify changing existing common
functions in an inconsistent and ad hoc way and making them
platform-specific unnecessarily.  If such functionality is necessary,
it should be provided in a platform-independent and consistent way.

Of course. I was just asking why you picked this specific behavior to make consistent across platforms.

If the existing X11 behavior is actually in use somewhere, then that makes sense, of course.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]