Re: CamelSeekableSubstream prob

On Mon, 2006-11-20 at 01:58 +0100, Philip Van Hoof wrote:
> It looks like the seekable-substream type is being used to wrap steams
> that are already seekable (like the memory stream).
> 
> If it does, it often upgrades the position member by adding (+=) the
> amount of bytes that where written and read. If the underlying one also
> does this (with the same integer), then the offset will be wrong.

Hmm, no. Forget about this patch. I still have the problem and the
seekable position integer isn't the same as the parent's seekable
position integer.

Searching some more ... (fearing it's an overflow problem that gets
triggered more often on ARM)


-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be 
gnome: pvanhoof at gnome dot org 
http://www.pvanhoof.be/blog