From: Hans Ronne <hronne@comhem.se>
To: Eric McDonald <mcdonald@phy.cmich.edu>
Cc: xconq7@sources.redhat.com
Subject: Re: IMFApp Office
Date: Sun, 08 Aug 2004 22:52:00 -0000 [thread overview]
Message-ID: <l03130301bd3b2f80f7e8@[212.181.162.155]> (raw)
In-Reply-To: <41157BB9.50508@phy.cmich.edu>
>> This is because your images have non-standard sizes.
>
>I realize they have non-standard sizes, but that should not cause black
>patches to appear at various places around the images in 32x32 grid
>boxes (whereas there are no display problems with the scaled images in
>the 32x32 closeup view).
Strange. I don't see any black patches under either Mac OS or Linux/X11.
The only thing I see is the failure to scale the images correctly on the
first attempt.
>I saw the 44x48 images, and assumed that Xconq would scale the images
>based on that. The reason I chose a height of 64 is so that it would fit
>the largest view size without having to be scaled back up from 32x32.
That's a nice idea. Images at 64x64 are generally so ugly that I never use
that magnification. And it seems that scaling of your images works, after
some initial confusion, both at 32x32 and 64x64.
>> However, a further complication is during actual drawing, when best_image
>> checks that no image is greater than 32x32 (or 44x48) and scales the image
>> in that is the case. Your images, if used in Xconq, would therefore be cut
>> to half-size before they are drawn.
>
>This is what I want. But, at the largest magnification factor, shouldn't
>Xconq be attempting to draw actual 64x64's if they exist?
That's also what it does, at least under Mac TCL.
>> P.S. Another strange thing that you may have noticed is that your new gif
>> appears (distorted) when you select wreckreation in the new game list.
>
>Hadn't tested it. My copy of Wreckreation is still in mid-hack and not
>in a usable state.
Well, let me modify that. On the Mac, the image gets distorted (i.e.
expanded to 240 x 160 pixels). In the tcltk interface, however, a smaller
image is drawn instead.
Hans
next prev parent reply other threads:[~2004-08-08 1:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 1:31 Improved IMFApp Hans Ronne
2004-08-04 1:59 ` Eric McDonald
2004-08-04 17:57 ` Hans Ronne
2004-08-04 18:46 ` Eric McDonald
2004-08-05 2:27 ` Hans Ronne
2004-08-05 3:18 ` Eric McDonald
2004-08-05 16:17 ` Jim Kingdon
2004-08-05 17:12 ` IMFApp Office (was Re: Improved IMFApp) Eric McDonald
2004-08-06 17:52 ` IMFApp Office Hans Ronne
2004-08-08 0:34 ` Eric McDonald
2004-08-08 1:02 ` Hans Ronne
2004-08-08 1:34 ` Eric McDonald
2004-08-08 22:52 ` Hans Ronne [this message]
2004-08-10 10:22 ` Eric McDonald
2004-08-10 13:25 ` Hans Ronne
2004-08-10 15:21 ` Eric McDonald
2004-08-10 19:02 ` Hans Ronne
2004-08-10 19:50 ` Eric McDonald
2004-08-10 20:44 ` Hans Ronne
2004-08-11 2:28 ` Eric McDonald
2004-08-11 2:30 ` Eric McDonald
2004-08-11 8:52 ` Eric McDonald
2004-08-11 15:55 ` Hans Ronne
2004-08-11 17:00 ` Eric McDonald
2004-08-12 1:56 ` Hans Ronne
2004-08-04 9:50 ` Improved IMFApp 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='l03130301bd3b2f80f7e8@[212.181.162.155]' \
--to=hronne@comhem.se \
--cc=mcdonald@phy.cmich.edu \
--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).