From: Daniel Colascione <dancol@dancol.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 10397@debbugs.gnu.org
Subject: bug#10397: [PATCH] Under Remote Desktop, NUMCOLORS is unreliable; workaround
Date: Thu, 29 Dec 2011 08:42:37 -0800 [thread overview]
Message-ID: <4EFC987D.2020901@dancol.org> (raw)
In-Reply-To: <CAAeL0SQq56w19b8F=b7G+pt1Gg-pjTL8-tmOFXHs_YW0tBoY1g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
On 12/29/11 8:27 AM, Juanma Barranquero wrote:
> On Thu, Dec 29, 2011 at 17:23, Daniel Colascione <dancol@dancol.org> wrote:
>
>> Why? What's the point of adding the extra complexity?
>> Setting cap to -1 leads to this line
>>
>> 1 << min (dpyinfo->n_planes * dpyinfo->n_cbits, 24);
>>
>> which produces a reasonable result for direct color displays.
>> Why keep using NUMCOLORS, which we know to be broken?
>
> No, you said that NUMCOLORS is known to be broken in a very specific
> case. In the general, non-RemoteDektop case, it works.
I'm not convinced there aren't other bugs lurking in the code backing
NUMCOLORS; after all, it's doing the same simple calculation we are, and
it's somehow doing it wrong.
http://msdn.microsoft.com/en-us/library/dd144877%28v=VS.85%29.aspx#3
suggests that NUMCOLORS is generally flaky.
> Can you
> guarantee that for every non-palettized display, it will produce the
> same number? Because otherwise you're changing the current behavior
> for people who's not affected by the RemoteDeskopt-related bug.
No, I can't guarantee that my original change always produces the same
results: it might fix other bugs.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
next prev parent reply other threads:[~2011-12-29 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:05 bug#10397: [PATCH] Under Remote Desktop, NUMCOLORS is unreliable; workaround Daniel Colascione
2011-12-29 16:13 ` Juanma Barranquero
2011-12-29 16:23 ` Daniel Colascione
2011-12-29 16:27 ` Juanma Barranquero
2011-12-29 16:42 ` Daniel Colascione [this message]
2011-12-29 16:45 ` Juanma Barranquero
2011-12-29 22:59 ` Daniel Colascione
2011-12-29 23:10 ` Juanma Barranquero
2011-12-29 23:13 ` Daniel Colascione
2011-12-29 23:18 ` Juanma Barranquero
2011-12-30 3:07 ` Juanma Barranquero
2011-12-30 3:18 ` Daniel Colascione
2011-12-30 8:51 ` Eli Zaretskii
2011-12-30 9:00 ` Eli Zaretskii
2011-12-30 12:24 ` Juanma Barranquero
2012-08-07 17:13 ` Eli Zaretskii
2012-08-07 17:33 ` Daniel Colascione
2012-08-07 18:07 ` Eli Zaretskii
2016-02-25 6:25 ` Lars Ingebrigtsen
2016-12-13 0:04 ` Glenn Morris
2011-12-30 1:04 ` Jason Rumney
2011-12-30 1:10 ` Daniel Colascione
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EFC987D.2020901@dancol.org \
--to=dancol@dancol.org \
--cc=10397@debbugs.gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).