Re: Global Interface Table Problem.
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Wed, 17 May 2006 11:16:04 -0400
Dinesh Venugopalan <dinesh@xxxxxxxxxxx> wrote:
The problem I am facing is this.
Lets say we have 2 IE window A and B. Where A is the
primary window and B is create by doing "file" -> "new" on A.
If the pointers are created in A and if I close A and record in B my
GIT queries work properly.
But if I create pointers in B, close the B window and record in A.
GIT query fails and returns the error values as 0x80070057 which
translates to "The parameter is incorrect".
The apartment (thread) in which the COM object was created is dead, and
the object died with it.
Personally, I'd not use a COM object in this scenario at all. Why not
just implement a regular C++ class in your DLL? Or perhaps a COM-like
object, but don't use COM mechanisms for creting and managing it. Just
make the object thread-safe and share it directly in a global variable.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925
.
- Follow-Ups:
- Re: Global Interface Table Problem.
- From: Dinesh Venugopalan
- Re: Global Interface Table Problem.
- References:
- Global Interface Table Problem.
- From: Dinesh Venugopalan
- Global Interface Table Problem.
- Prev by Date: Global Interface Table Problem.
- Next by Date: Re: Wierd MS Word problem with windowed controls
- Previous by thread: Global Interface Table Problem.
- Next by thread: Re: Global Interface Table Problem.
- Index(es):
Relevant Pages
|
