Click here to Skip to main content

C / C++ / MFC

Re: Vector is losing varable data

Larry Mills Sr15-Sep-08 2:52

15-Sep-08 2:52

I found the error here:
When I initialize the copy constructor I left out the m_csExtra1 and m_csExtra2 varables so naturally it couldn't copy them!.
Thanks anyway.

A C++ programming language novice, but striving to learn

George_George11-Sep-08 16:25

11-Sep-08 16:25

Hello everyone,

Sorry for asking this simple question. I found after some coding, I have some new understanding of the concept. Now I think dual interface means the com object inherits from IDispatch, and since IDispatch inherits from IUnknown, the COM consumer could choose to use IDispatch or IUnknown, so called dual interface.

For non-dual interface, I think it means the com object only implements interface IUnknown.

My understandings are both correct?

thanks in advance,
George

Re: dual interface

Steve Echols11-Sep-08 19:59

11-Sep-08 19:59

Dual interface refers to supporting both IDispatch and a VTBL, which means you can call it through COM using QueryInterface or from C++ directly. Been so long since I've done it, I'm a bit fuzzy on the details.

- S
50 cups of coffee and you know it's on!
A post a day, keeps the white coats away!

Re: dual interface

George_George11-Sep-08 20:21

11-Sep-08 20:21

Thanks Steve,

I.

Does it means 1 or 2?

1. my coclass implements IDispatch directly, is my coclass dual-interface?

2. my coclass implements some customized interface, and the customized interface implements IDispatch, is my coclass dual-interface?

II.

My confusion is dual means (IDispatch/IUnknown) or (IDispatch/customized interface)?

regards,
George

Re: dual interface

SandipG 11-Sep-08 20:28

11-Sep-08 20:28

Hi George,
Read this link about implementing Dual interfaces. I think things shoudl be clear after this.
Dual Interface[^]

George_George wrote:
My confusion is dual means (IDispatch/IUnknown) or (IDispatch/customized interface)?

I think dual interface does not mean two interfaces its about the ways you can access methods.

I hope it helps..

Regards,
Sandip.

Re: dual interface

George_George11-Sep-08 20:34

11-Sep-08 20:34

Thanks Sandip,

1.

I have read it. But still confused. Does it mean if my coclass implements IDispatch directly, my coclass is a dual interface? Smile | :)

Smile | :)

2.

Two ways to access (dual), you mean one way of using IDispatch and the other way of using IUnknown? Or something else?

regards,
George

Re: dual interface

SandipG 11-Sep-08 20:38

11-Sep-08 20:38

George_George wrote:
Two ways to access (dual), you mean one way of using IDispatch and the other way of using IUnknown? Or something else?

No i Think

1. Add an entry (or entries) to the COM map to expose the dual interface through QueryInterface.

2. Implement the vtable part of the interface in your class.

George_George wrote:
I have read it. But still confused. Does it mean if my coclass implements IDispatch directly, my coclass is a dual interface? Smile

If you implement the second step in your class..

Does it help..

Regards,
Sandip.

Re: dual interface

George_George11-Sep-08 20:50

11-Sep-08 20:50

Thanks Sandip,

1.

I am still confused. Dual interface means two ways to invoke methods of my class. One of them is through IDispatch.Invoke, the other way is?

2.

Confused about what do you mean -- "Implement the vtable part of the interface in your class."

If my class have virtual methods, it should have vtable, what do you mean implement the vtable part?

regards,
George

Re: dual interface

CPallini11-Sep-08 21:54

11-Sep-08 21:54

George_George wrote:
1.

I am still confused. Dual interface means two ways to invoke methods of my class. One of them is through IDispatch.Invoke, the other way is?

Via another interface's VTABLE.

George_George wrote:
2.

Confused about what do you mean -- "Implement the vtable part of the interface in your class."

Suppose you have (only) a method (say Add) you can use via IDispatch::Invoke. Implement the VTABLE part of the interface means: provide an interface, say IOperation exposing the Add method (since such method is not directly exposed by IDispatch).
Possibly the final COM component interface inherits both from IDispatch and IOperation, as Sandip I don't remember the technical details and, as usual: "this in going on my arrogant assumptions..."
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: dual interface

George_George11-Sep-08 21:58

11-Sep-08 21:58

Thanks CPallini,

I have did more study and I want to share my points here. Could you help to
review whether my points are correct please? Smile | :)

Smile | :)

1. If a component implements IDispatch directly, we can only invoke its
member methods through IDispatch.Invoke -- only one way, so it is not dual
interface;

2. If a component implements IUnknown directly, we can only use
AddRef/Release/QueryInterface, it is useless since we can only use the 3
methods;

3. If a component implements a customized interface, then the customized
interface implements IUnknown, then we could invoke the component's member
methods through QueryInterface to get the customized interface, and using the
vtable in the customized interface to invoke member methods. But still one
way, so it is not dual interface;

4. If a component implements a customized interface, then the customized
interface implements IDispatch, then we could invoke the component's member
methods through QueryInterface to get the customized interface, and using the
vtable in the customized interface to invoke member methods, and also we
could invoke through IDispatch.Invoke. Two ways to invoke it, so called dual
interface.

All of my understandings are correct? Anything missing? Smile | :)

Smile | :)

regards,
George

Re: dual interface

CPallini11-Sep-08 22:11

11-Sep-08 22:11

IMHO your understandings are correct.

Point (2), as it stands, IMHO is misleading: since IUnknown implementation is mandatory, I will say: if a component implements only IDispatch...
But such a point is obvious.

Also, as you know well, IDispatch, like any other COM interface must provide IUnknown, then saying: "implementing only IDispatch" it is equivalent to say: "implementing a IUnknown whose QueryInterface method may return only IDispatch".
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: dual interface

George_George11-Sep-08 23:02

11-Sep-08 23:02

Thanks CPallini!

http://www.codeproject.com/script/Forums/View.aspx?fid=1647&msg=2720744[^]

Your reply is very clear. I post my further question here. Do you have any ideas? Smile | :)

Smile | :)

regards,
George

Re: dual interface

Swathee11-Sep-08 22:44

11-Sep-08 22:44

When you say a component implements IDispatch or IUnknown im assuming that you have an interface IX that is derived from either of those interfaces (IDispatch or IUnknown)and you are implementing those intrefaces in a coclass.

1. Any COM interface has to be derived from IUnknown. So when you implement IDispatch you also have to implement IUnknown, because IDispatch is also derived from IUnknown.

Any interface,say IX, that is derived from IDispatch is a dual interface. Because IX methods can be invoked through IDispatch methods as well as vtable.

2. You can also derive your interface IX from IUnknown and invoke its methods through vtable.

3,4. Don't know what you mean by customized interface.

May i suggest that you go through "Inside COM" by Dale Rogerson. It is a very good book it will help you in understanding COM much better.

Re: dual interface

George_George11-Sep-08 23:09

11-Sep-08 23:09

Thanks sw@thi,

1.

You mentioned twice about "invoke its methods through vtable". My confusion is what exactly mean "through vtable". I think you mean QueryInterface for interface IX for the coclass object, and invoke the exposed methods in IX is through vtable of coclass object for interface IX. Correct?

2.

sw@thi wrote:
3,4. Don't know what you mean by customized interface.

Customized interface I mean any C++ eligible interface which is not IDispatch and IUnknown, and in 3 the customized interface inherits IUnknown and in 4 the customized interface inherits IDispatch. From my description, do you think my points for 3 and 4 are both correct?

regards,
George

Re: dual interface [modified]

SandipG 11-Sep-08 22:13

11-Sep-08 22:13

Hi CPallini,
I am not sure that we require an extra Interface. Check this Link Dual Interfaces[^]
I could not find some good sample for this do you have one which will explain step by step procedure.. I am asking for this because i have never implemented this ..

CPallini wrote:
Sandip I don't remember the technical details and, as usual: "this in going on my arrogant assumptions..."
Smile

Laugh | :laugh:

Regards,
Sandip.

modified on Friday, September 12, 2008 4:31 AM

Re: dual interface

CPallini11-Sep-08 22:33

11-Sep-08 22:33

I think you're right, since you may simply do something like:

class IMyDualInterface : public IDispatch

with a VTABLE arranged the following way:

- QueryInterface methods
- IDispatch methods
- 'Add' method here.

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: dual interface

George_George11-Sep-08 22:56

11-Sep-08 22:56

Thanks CPallini,

I am a little losing the context and my English is not very good.

Do you guys mean in order to implement a dual interface,

- we need an additional customized interface, which implements IDispatch?

- or we need implement both an additional customized interface (and the customized interface inherits from IUnknown) and also implement IDispatch?

- or both the above two ways are fine?

regards,
George

Re: dual interface

CPallini11-Sep-08 23:05

11-Sep-08 23:05

We need a customized interface that implements (also) IDispatch (Usually it inherits from IDispatch, that in turn, inherits from IUnknown).
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: dual interface

SandipG 11-Sep-08 23:12

11-Sep-08 23:12

Hi CPallini,
I didn't find any simple article or example to do this on CP, which will explain steps.
Do you know any?

If not i think George can write one side by side as he implements Dual Interface Smile | :)

Smile | :)

Regards,
Sandip.

Re: dual interface

George_George11-Sep-08 23:14

11-Sep-08 23:14

I am also asking for this, about various ways to implement dual interface.

regards,
George

Re: dual interface

CPallini11-Sep-08 23:32

11-Sep-08 23:32

SandipG wrote:
Do you know any?

Unfortunately, no. Sigh | :sigh:

Sigh | :sigh:

SandipG wrote:
If not i think George can write one side by side as he implements Dual Interface

Oh, he's writing the George's COM Bible!
Big Grin | :-D

Big Grin | :-D

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

modified on Friday, September 12, 2008 5:39 AM

Re: dual interface

George_George11-Sep-08 23:13

11-Sep-08 23:13

Thanks CPallini,

I have one more comment, at first I agree with what you mean above. I think there is another way to implement dual interface, which is we need implement both an additional customized interface (and the customized interface inherits from IUnknown) and also implement IDispatch (in IDispatch's Invoke implementation we can call the methods from the customized interface methods' implementation)? Is that also dual interface?

regards,
George

Re: dual interface

CPallini11-Sep-08 23:45

11-Sep-08 23:45

I think the standard way is just inheriting from IDispatch (since IDispatch in turn inherits from IUnknown) this way does not prevent IDispatch::Invoke to call the methods of the customized interface.
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Re: dual interface

George_George11-Sep-08 23:48

11-Sep-08 23:48

I agree, but my implementation above is wrong and not dual interface, CPallini?

regards,
George

Re: dual interface

CPallini12-Sep-08 0:44

12-Sep-08 0:44

Well, it depends on how do you implement the IDispatch interface (for instance, if your customized interface inherits both from IUnknown and IDispatch the you've a undesirable diamond inehritance path).
Smile | :)

Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

General News Suggestion Question Bug Answer Joke Praise Rant Admin

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.