Remy as always, your right!
It isn't the indy component which was giving me greif, it was the Indy demo!
The commandhandler server was using a case statement for a TComboBox
integer - unfortunately sending the command with a parameter made the
itemindex be returned as -1 - there was no case for -1 and thus it wasn't
reading using ReadLn!
Sorted that, and put a ReadLn into a repeat-Until loop with a readln
timeout, and a boolean to indicate if anything was read. Works perfectly
now.
Thx Remy
JD
"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
news:47261f1b@newsgroups.borland.com...
>
> "Jamie Dale" <jamie.dale@yahoo.com> wrote in message
> news:47251956$1@newsgroups.borland.com...
>
>> Just to add more to this, the CommandHandlers ParseParams
>> ability doesn't seem to work.
>
> Yes, it does, and has worked well for a very long time. Why do you think
> it does not work? Please provide an example.
>
>> In the events triggered by the commandhandler there is no way
>> of accessing the params that are supposed to be parsed
>
> Yes, there is - the Params and UnparsedParams properties of the TIdCommand
> class. When ParseParams is True, use the Params property. When
> ParseParams is False, use the UnparsedParams property instead.
>
>> not that they are
>
> Yes, they are.
>
>
> Gambit
