On Wed, 15 Oct 2008 17:34:12 +0300
Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> Colin D Bennett wrote:
> > On Tue, 14 Oct 2008 00:11:42 +0300
> > Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> >> As we have same handle all the time for bitmap we can just
> >> continue to use it as is. If we woul
Colin D Bennett wrote:
> On Tue, 14 Oct 2008 00:11:42 +0300
> Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> A minor point: You mentioned "RGB" and "RGBA" format--do you mean "true
> color" (either RGB[A] or BGR[A] layout) or do you mean literal RGB byte
> order? If we are talking about picking a
On Tue, 14 Oct 2008 00:11:42 +0300
Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> Colin D Bennett wrote:
> > On Mon, 13 Oct 2008 21:27:46 +0300
> > Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> >> Idea is that if bitmap is still locked you cannot optimize it or
> >> you cannot lock it again. And
Colin D Bennett wrote:
> On Mon, 13 Oct 2008 21:27:46 +0300
> Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
>> Idea is that if bitmap is still locked you cannot optimize it or you
>> cannot lock it again. And if bitmap is optimized you cannot get
>> pointer to modify it. Eg. Function call returns me
On Mon, 13 Oct 2008 21:27:46 +0300
Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> Colin D Bennett wrote:
> > On Fri, 03 Oct 2008 23:16:51 +0300
> > Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> >> I have been thinking this a bit and I think best solution to
> >> bitmaps is something like followin
Colin D Bennett wrote:
> On Fri, 03 Oct 2008 23:16:51 +0300
> Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
>> I have been thinking this a bit and I think best solution to bitmaps
>> is something like following.
>>
>> Two types of bitmap: easily accessible and optimized bitmaps for
>> hardware.
>>
>
On Fri, 03 Oct 2008 23:16:51 +0300
Vesa Jääskeläinen <[EMAIL PROTECTED]> wrote:
> Vesa Jääskeläinen wrote:
> > Vesa Jääskeläinen wrote:
> >> It is really necessary that all generic graphical menu code like
> >> bitmap scaler works always. Not just for some optimized formats as
> >> otherwise it wo
Vesa Jääskeläinen wrote:
> Vesa Jääskeläinen wrote:
>> It is really necessary that all generic graphical menu code like bitmap
>> scaler works always. Not just for some optimized formats as otherwise it
>> would render graphical menu unusable in some cases. It can be not so
>> pretty on low end sys
Vesa Jääskeläinen wrote:
> It is really necessary that all generic graphical menu code like bitmap
> scaler works always. Not just for some optimized formats as otherwise it
> would render graphical menu unusable in some cases. It can be not so
> pretty on low end systems, but it should at least wo
Vesa Jääskeläinen wrote:
> Colin D Bennett wrote:
>> This patch adds image scaling support. Nearest neighbor and bilinear
>> interpolation algorithms are supported.
>>
>> The gfxterm background_image command scales the background image to fit
>> the screen. This can be controlled with the new --m
Colin D Bennett wrote:
> This patch adds image scaling support. Nearest neighbor and bilinear
> interpolation algorithms are supported.
>
> The gfxterm background_image command scales the background image to fit
> the screen. This can be controlled with the new --mode/-m option.
Copyrights year
This patch adds image scaling support. Nearest neighbor and bilinear
interpolation algorithms are supported.
The gfxterm background_image command scales the background image to fit
the screen. This can be controlled with the new --mode/-m option.
Regards,
Colin
=== modified file 'conf/i386-pc.r
12 matches
Mail list logo