Re: [palito-dev] quick impressions of 2003-05-21

[Michael Devey]

> You'll also note that when you tell a large group of planes to go to a
> common point, they (surprisingly :) arrive scatered arount that point.

heh yeah it's getting there - I've presently got 8 playing "round and round the 
mullberry bush like a [confused] teddybear"  But that's all due to the fact 
that they can be 'inside' one another - I figure it'll go away as soon as we 
give them state transitions to land (first one to lock out a landing space wins 
so to speak)

> Please tell me what #includes you had to put in what .c file so I can patch
> them here.

the 21st release - nothing all peachy :) - but I was playing with some pre 
20/21april/may ones and I think trying for something as high as possible made 
life easier (string.h and stdlib.h in game.h from memory) Not that it matters 
presently, but what I'm trying to say is that it's happened in the past quite a 
bit and I'm interested as to why (you obviously get it to compile on your 
machines, but on a debian box's it needs those libraries included) So atleast 
for any use of strlen you need string.h somewhere and exit stdlib.h.

I know I'm complaining about tarballs that aren't "releases" but anyway, I'm 
annoying :) (like for instance in one of the 15th releases you declared some 
variables not at the start of a block :P double dxy from memory - fine in c++ I 
know) 

> Anyway, have you tried the 3D terrain?
> There are some maps at http://palito.9hells.org/data/
> Try divide2.zip

yeah did - had a symbolic link the src 
divide2.bmp -> /home/barrett/data/palito/divide2.bmp
also the divide2.zip had a png and not a bmp in it? (I converted it) and it 
works good :)

but yeah png's would be better

myke