Udo Richter wrote:
Klaus Schmidinger wrote:
Well, we could introduce
cRemux::SetTimeouts(int PutTimeout, int GetTimeout) { resultBuffer->SetTimeouts(PutTimeout, GetTimeout); }
Klaus
Haven't gotten any response on this suggestion so far. Would this solve your problem?
Oh, sorry. Yes, of course, this would work. My current workaround is to gain access using dirty tricks, so this is welcome. Access to Available() may be useful too. Or, for a bigger rewrite, what about making class cRemux : public cRingBufferLinear?
cRemux::Get() returns the number of currently available bytes.
Klaus