[PATCH 1/8] riched20: Stub for ITextRange interface and implement ITextDocument::Range. (resend try 4)

Huw Davies huw at codeweavers.com
Fri Sep 12 02:53:53 CDT 2014


On Fri, Sep 12, 2014 at 10:47:44AM +0800, Jactry Zeng wrote:
> 
> 2014-09-12 4:43 GMT+08:00 Sebastian Lackner <sebastian at fds-team.de>:
> >
> >
> > Are you sure? Doesn't this test below show exactly the opposite? It seems to
> be safe
> > to release the ITextDocument, and afterwards call an ITextRange function - it
> will just
> > return CO_E_RELEASED since the parent object was already released. Or am I
> misunderstanding
> > this code?
> 
> So sorry, I made a mistake yesterday here. I added more a ITextRange::Release
> before the ITextRange calling
> in my new tests code yesterday.
> Functions of ITextRange will return CO_E_RELEASED after reOle/txtDoc were
> released and will
> crash after the ITextRange was released.

In that case let's go with your proposed implementation.

Huw.



More information about the wine-devel mailing list