[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [palito-dev] input.c TELL_SELECT_COMMANDER
From: |
Michael Devey |
Subject: |
Re: [palito-dev] input.c TELL_SELECT_COMMANDER |
Date: |
Sat, 20 Sep 2003 10:17:14 +1000 |
User-agent: |
Mutt/1.5.4i |
wrrrrrr
Well you could make a variable that holds the commander_index_pos or the
commander directly. I sodomise the commander every time I test something.
Support me in this endeavor and make the period of pain shorter for him?
And just to be annoying - why the reshuffle of index's? Personally I think
unsigned with id 0 to empty.
myke
On Fri, Sep 19, 2003 at 03:46:28PM -0300, address@hidden wrote:
> On Fri, Sep 19, 2003 at 10:01:54PM +1000, Michael Devey wrote:
> > I'm sure this just slipped through on a regexp replacement and you just
> > couldn't be fodased figuring out what went wrong so here it is.
> thanks.. but anyway i'm not very comfortable with this assumption that
> the commander is always the first unit in the array..
> and i also plan to change the id 0 to be valid (and put the commander there),
> using -1 to indicate an empty slot.
>
> []'s barrett
>
>
> _______________________________________________
> palito-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/palito-dev