Re: [crossfire] first bug discovered by unit test

2006-03-14 Thread Alex Schultz
This reminds me of one idea that I had for the functional tests. Since some tests would require some sort of client to connect, I was thinking about doing this: Fixing up the python client libs that I had a start on. In a functional test map that wants a 'player', make a script that uses crossfi

Re: [crossfire] first bug discovered by unit test

2006-03-14 Thread Tchize
Mark Wedel a écrit : > Random question - is there any framework in place for external functional > tests? > > > no > I ask because to reproduce and confirm I fixed the setup buffer overflow > bug, >I do have an external perl script which would be nice to toss somewhere. > >___

Re: [crossfire] map2 & animations

2006-03-14 Thread Mark Wedel
Brendan Lally wrote: > This would therefore suggest that a better approach would be to have 1 > byte at the start of the map2 packet to act as a control byte, > something like > > CDDDNSEW > > where C corresponds to the newmap packet, and tells the client to > clear the fog of war data. > > D i

Re: [crossfire] first bug discovered by unit test

2006-03-14 Thread Mark Wedel
Random question - is there any framework in place for external functional tests? I ask because to reproduce and confirm I fixed the setup buffer overflow bug, I do have an external perl script which would be nice to toss somewhere. ___ crossfire

Re: [crossfire] map2 & animations

2006-03-14 Thread Mark Wedel
Tchize wrote: > Mark Wedel a écrit : > quick comment on one point. I agree on principle but about 3: > > The principle of leaving this case server side is ok, but maybe another > suggestion is > send it has a phased animation which doesn't repeat. Of course you can > get a gap between server state