From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: Elijah Meeks <elijahmeeks@yahoo.com>,
xconq7@sources.redhat.com, xconq-hackers@lists.sourceforge.net
Subject: Re: Reduced Image Quality for 32x32 Pixel Units
Date: Sun, 12 Dec 2004 03:27:00 -0000 [thread overview]
Message-ID: <41BBB053.2030402@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.53.0412112100200.12327@opal.ansuz.sooke.bc.ca>
mskala@ansuz.sooke.bc.ca wrote:
> Another possible way of dealing with it might be to change the APIs so
> that the interface can request from the kernel "Give me an image somewhere
> in this range of sizes, and try to avoid scaling if possible."
This is what I was looking into earlier today in response to Elijah's
bug report. It seems that 'best_image' could be modified to take "int
w1, int h1, int w2, int h2" instead of "int w, int h". Probably we would
want to change its name to 'best_image_in_range' or something like that.
For backwards compatibility, we then make a 'best_image' function which
calls 'best_image_in_range' with w1 == w2 and h1 == h2. I started to
look at the logic involved, but got distracted by other things. I could
probably make the changes, but I would be much more comfortable if you
did, Matthew.
> I'm starting to get a rough idea of what API changes need to be made.
> Maybe it'd be appropriate to do the CVS-branch thing,
I'll try to get around to setting up a branch in CVS tomorrow. As long
as the yellow pixels problem and low res pixel color problems are fixed
before 7.5.0, I don't really care how long development goes on in a
special branch.
> FWIW, I actually like the blocky look of the scaled images, but I'm
> guessing I'm in the minority there.
I have mixed feelings about it. But, I have an old monitor with a
not-so-good dot pitch, so the way I see things on screen is generally
not as clearly as people using sharper monitors.
Eric
next prev parent reply other threads:[~2004-12-12 2:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 0:04 Isometric images, sattelite images, and rotation mskala
2004-12-05 2:24 ` Eric McDonald
2004-12-05 4:59 ` Elijah Meeks
2004-12-05 10:27 ` Isometric images, satellite " mskala
2004-12-11 3:58 ` Eric McDonald
2004-12-11 4:20 ` Attribute System Elijah Meeks
2004-12-12 1:13 ` Eric McDonald
2004-12-12 2:11 ` Reduced Image Quality for 32x32 Pixel Units Elijah Meeks
2004-12-12 2:43 ` mskala
2004-12-12 3:27 ` Eric McDonald [this message]
2004-12-12 3:33 ` mskala
2004-12-12 4:21 ` Eric McDonald
2004-12-12 4:17 ` Elijah Meeks
2004-12-12 19:05 ` Eric McDonald
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41BBB053.2030402@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=elijahmeeks@yahoo.com \
--cc=mskala@ansuz.sooke.bc.ca \
--cc=xconq-hackers@lists.sourceforge.net \
--cc=xconq7@sources.redhat.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.
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).