Re: Find out caller of IDispatch::Invoke
- From: "Igor Tandetnik" <itandetnik@xxxxxxxx>
- Date: Tue, 13 Jun 2006 16:43:57 -0400
dimitrov <s_d_dimitrov@xxxxxxxxx> wrote:
I have a IDispatch implementation, that receives calls from two
different objects ( both of them InternetExplorer - IWebBrowser2 ).
The funny thing is that I cannot find out who is currently calling,
which leads to some pretty comical situations.
Is there a way to get who the caller is?
Or would you suggest creating two different IDispatch implementations,
each one receiving calls from just one object?
Yes, that's what I would suggest.
In this case ( with 2 IDispatch implementations ) I would like to ask:
Is it possible to have regular C++ class implement IDispatch and
creating it just with "new" without making it COM object, registering
it in registry and so on?
Yes. You only need registration if your object has to be creatable by
external clients, with CoCreateInstance and such. You can happily have
internal objects that are not registered.
--
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: Find out caller of IDispatch::Invoke
- From: dimitrov
- Re: Find out caller of IDispatch::Invoke
- References:
- Find out caller of IDispatch::Invoke
- From: dimitrov
- Find out caller of IDispatch::Invoke
- Prev by Date: Find out caller of IDispatch::Invoke
- Next by Date: Re: Find out caller of IDispatch::Invoke
- Previous by thread: Find out caller of IDispatch::Invoke
- Next by thread: Re: Find out caller of IDispatch::Invoke
- Index(es):
Relevant Pages
|