From: Daniel Colascione <dancol@dancol.org>
To: Jason Rumney <jasonr@gnu.org>
Cc: 10397@debbugs.gnu.org
Subject: bug#10397: [PATCH] Under Remote Desktop, NUMCOLORS is unreliable; workaround
Date: Thu, 29 Dec 2011 17:10:44 -0800 [thread overview]
Message-ID: <4EFD0F94.8090406@dancol.org> (raw)
In-Reply-To: <877h1ehnu7.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
On 12/29/11 5:04 PM, Jason Rumney wrote:
> Daniel Colascione <dancol@dancol.org> writes:
>
>> Under remote desktop, Windows returns the wrong number of colors from
>> GetDeviceCaps (hdc, NUMCOLORS). I hit this bug myself, and MSDN
>> comments seem to indicate that others hit it as well. The workaround
>> seems harmless: on non-palettized displays, calculating the number of
>> display colors based on display bitness should produce good results.
>
> I've always been under the impression that this is deliberate, and
> related to the bandwidth that is available, so at least applications
> that want to improve performance over low bandwidth links can restrict
> their use of colors.
A remote desktop user can change the depth of the virtual display
presented to applications on the server. If a user wants to trade
fidelity for bandwidth, he can configure his client to use an 8bpp
visual. Some users (me) configure their clients for a relatively high
bit depth, but find that the OS lies to applications some of the time
(NUMCOLORS is wrong, but the display bitness is accurate). I think the
NUMCOLORS behavior is a real bug; if it weren't, the lie would be more
consistently presented.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 235 bytes --]
prev parent reply other threads:[~2011-12-30 1:10 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
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 [this message]
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=4EFD0F94.8090406@dancol.org \
--to=dancol@dancol.org \
--cc=10397@debbugs.gnu.org \
--cc=jasonr@gnu.org \
/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).