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: Thoughts on terrain imaging
Date: Wed, 24 Nov 2004 03:18:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0411231648280.16026-100000@diamond.ansuz.sooke.bc.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0411231422280.16849-100000@leon.phy.cmich.edu>

On Tue, 23 Nov 2004, Eric McDonald wrote:
> user account so that you can be added to the project as a 
> developer. I figure this might be easier than you submitting a 
> bunch of patches which people would have to apply if they wanted 
> to test out your work.

Okay - I'll sign up for one.

> For the per-cell case, you may want to implement new layers. I 
> believe that the 'aref' and 'aset' macros in 'world.h', IIRC, 
> would be worth looking at. (Layer allocation is handled elsewhere.)

Yes - that's one of the things I'm looking at.

> Regarding the bug reports: if you're offering to fix the bugs, 
> then that's great. If you would like some help fixing them, please 
> add them to the project's bug tracking system on Sourceforge, and 
> I will try to help you clear out some of them.

I'd like to spend a little more time trying to figure out what's going on
with these before I decide whether I can fix them easily myself, or want
to file them for other people to look at; I was just commenting about them
on the list in the hope that maybe you (or some other reader) would
instantly recognize either the bug or the mistake I'm making in the GDL to
cause the incorrect behaviour.

That image-rescaling code (which I've looked at a little more since
writing my last message here) seems to be a real dog's breakfast.  There
are a couple of points where it seems to be testing for error conditions
in the very next line after that code that guarantees that the error
condition can't happen, and there are other points where a comment
explaining what's about do be done is followed by a line of code that
clearly does something else.  I think those are signs it's been tweaked
and patched several times in the past, and it may be that the best thing
to do might be to simply rewrite those routines - not a project I had
contemplated as part of the map-image feature addition, but one I'm
willing to tackle if it turns out to be necessary.
-- 
Matthew Skala
mskala@ansuz.sooke.bc.ca                    Embrace and defend.
http://ansuz.sooke.bc.ca/

  reply	other threads:[~2004-11-23 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 16:44 mskala
2004-11-23 22:08 ` Eric McDonald
2004-11-24  3:18   ` mskala [this message]
2004-11-24  4:25     ` Eric McDonald
2004-11-24 13:00 ` Eric McDonald
2004-11-25  2:50   ` mskala

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.21.0411231648280.16026-100000@diamond.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).