[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: SmallMap issue(s)
From: |
Gervase Lam |
Subject: |
Re: SmallMap issue(s) |
Date: |
Sun, 13 Oct 2002 01:03:10 +0100 |
> Subject: Re: SmallMap issue(s)
> From: Ingo Ruhnke <address@hidden>
> Date: 10 Oct 2002 13:38:12 +0200
> Gervase Lam <address@hidden> writes:
> > As to indiana-yingwan.xml, one way to do it is as well as each
> > "object" having draw_smallmap(), they could also have
> > init_smallmap(unsigned char* cbuffer). This could/would write on to
> > the initial small map canvas.
>
> The problem is that there are two ways to 'draw' on the smallmap, one
> is to simple draw a surface above the colmap on the screen (via
> draw_smallmap()), the other would be indirectly to draw on the colmap,
> which then gets converted to the smallmap surface (no member function,
> smallmap does that itself). Well, the first is easy to solve, the
> second is quite a lot more difficult, since you can't just draw to the
> colmap without changing it.
In SmallMap::init(), buffer is a pointer to the colmap. cbuffer is just a
pointer to the Canvas that will eventually be the smallmap that will be
displayed on the screen. Therefore you can alter cbuffer without causing
colmap problems.
Thanks,
Gervase.
Re: SmallMap issue(s), Ingo Ruhnke, 2002/10/09
Re: SmallMap issue(s), Ingo Ruhnke, 2002/10/10
Re: SmallMap issue(s), Gervase Lam, 2002/10/09
Re: SmallMap issue(s), Gervase Lam, 2002/10/10
Re: SmallMap issue(s),
Gervase Lam <=
Re: SmallMap issue(s), Gervase Lam, 2002/10/13
Re: SmallMap issue(s), Gervase Lam, 2002/10/13