From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15489 invoked by alias); 12 Dec 2004 02:43:56 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 15462 invoked from network); 12 Dec 2004 02:43:53 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by sourceware.org with SMTP; 12 Dec 2004 02:43:53 -0000 Received: from [192.168.181.128] (c-67-176-41-158.client.comcast.net[67.176.41.158]) by comcast.net (sccrmhc12) with ESMTP id <2004121202435201200ihp5ge>; Sun, 12 Dec 2004 02:43:52 +0000 Message-ID: <41BBB053.2030402@phy.cmich.edu> Date: Sun, 12 Dec 2004 03:27:00 -0000 From: Eric McDonald User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) MIME-Version: 1.0 To: mskala@ansuz.sooke.bc.ca CC: Elijah Meeks , xconq7@sources.redhat.com, xconq-hackers@lists.sourceforge.net Subject: Re: Reduced Image Quality for 32x32 Pixel Units References: <20041212011304.61237.qmail@web13122.mail.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004/txt/msg01472.txt.bz2 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