public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: mskala@ansuz.sooke.bc.ca
Cc: xconq7@sources.redhat.com
Subject: Re: Terrain images proposal
Date: Mon, 27 Sep 2004 18:05:00 -0000	[thread overview]
Message-ID: <41571623.5020506@phy.cmich.edu> (raw)
In-Reply-To: <Pine.LNX.4.21.0409261434500.25902-100000@diamond.ansuz.sooke.bc.ca>

mskala@ansuz.sooke.bc.ca wrote:

> Whichever one the designer specified last - just like properties and table
> entries. 

That's probably fine.

> The idea is that the cell
> only *has* one image; 

Well sure. I don't think either of us would dispute that.

>>But, I had thought that you were suggesting that whole rectangles 
>>(spanning multiple cells) simply be embedded into the map at given 
>>coordinates. Based on your response, I think this is not what you 
>>actually had in mind....
> 
> What I had in mind was that you specify a roughly rectangular region of
> cells (yes, it'll have wiggly borders because it's made up of hexes) so
> that each one of them is clipped from the image in much the way hexes are
> already clipped from images. 

Right. I figured that this is what you meant from your previous 
response. This is reasonable; I see no real issues with it.

> The region
> stops hard at the hex boundaries, though.

I think this is the only part of your proposal that I was initially 
unclear about.

Eric

      reply	other threads:[~2004-09-26 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 15:24 mskala
2004-09-26 16:30 ` Eric McDonald
2004-09-26 16:43   ` mskala
2004-09-26 17:30     ` Eric McDonald
2004-09-26 17:55       ` mskala
2004-09-26 18:23         ` Eric McDonald
2004-09-26 19:19           ` mskala
2004-09-27 18:05             ` Eric McDonald [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=41571623.5020506@phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=mskala@ansuz.sooke.bc.ca \
    --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).