Re: SmallMap issue(s)

[Gervase Lam]

> Subject: Re: SmallMap issue(s)
> From: Ingo Ruhnke <address@hidden>
> Date: 09 Oct 2002 01:24:38 +0200

> SmallMap::draw()
> {
>         world->draw_smallmap(this);
> }
> [...]
> void
> Exit::draw_smallmap(SmallMap* smallmap)
> {
>   smallmap->draw_surface(exit_surface, pos);
> }

Anyway, do you "worldobj->draw_smallmap(this)", not 
"world->draw_smallmap(this)"?  I assume that an iterator will have to be 
used to go through all of the objects so that each object's 
draw_smallmap() is called?  If so, would it slow things down as it as to 
go through every object?

Btw, though I've learnt C++, I need to put it into practice.  This is why 
I'm here!  Oh yes, I do like Lemmings as well!

> BTW. We also need a way to 'disable' the colmap so that a user can not
> see clearly where the exits and the ground is, indiana-yingwan.xml and
> fake_exits are the reason for this.

Hmmm.  Starting with fake_exits, probably the best thing to do would be to 
have a draw_smallmap() for it as well (or draw_onto_smallmap() is what I'd 
prefer to call it).

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 technique indiana-yingwan.xml uses is to have a hotspot instead of 
solid or ground.  What exactly is a hotspot?  Hopefully having all 
hotspots being drawn on to the small map is allowed.

Thanks,
Gervase.