public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: mskala@ansuz.sooke.bc.ca
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com, xconq-hackers@lists.sourceforge.net
Subject: Re: Reduced Image Quality for 32x32 Pixel Units
Date: Sun, 12 Dec 2004 03:33:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.53.0412112219290.12327@opal.ansuz.sooke.bc.ca> (raw)
In-Reply-To: <41BBB053.2030402@phy.cmich.edu>

On Sat, 11 Dec 2004, Eric McDonald wrote:
> 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'll try building a best_image_in_range function in the kernel - that
should be easy - but I'm not sure about the interface side of the
equation.  I think that there's a TCL command implemented for the purpose
of requesting unit images (possibly even the same one you were looking at
with those crashing bugs I filed recently) and that command will need its
syntax changed or something to deal with the additional arguments, and
then the TCL code that actually uses that command will need to be updated
too.  Presumably similar changes on the SDL side, although I'm even less
sure of the details there.

Now, if there isn't an image in the range and it has to scale, to what
size should it scale?  I'm thinking maybe it should go to the largest end
of the range - it's going to look blocky for being scaled anyway, so it
might as well at least be big - but would it be better to have a third
width/height pair as well, to be the size to scale to if scaling is
necessary?

> 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.

Low-res pixel color problem = the issue of some terrain types disappearing
at the lowest magnification, right?
-- 
Matthew Skala
mskala@ansuz.sooke.bc.ca                    Embrace and defend.
http://ansuz.sooke.bc.ca/

  reply	other threads:[~2004-12-12  3:27 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
2004-12-12  3:33                 ` mskala [this message]
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=Pine.LNX.4.53.0412112219290.12327@opal.ansuz.sooke.bc.ca \
    --to=mskala@ansuz.sooke.bc.ca \
    --cc=mcdonald@phy.cmich.edu \
    --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).