Title: RE: [msvc] Automation, IDispatch, Class Explosing The Interface

> Attempting to access the C++ object itself from the interface pointer is
> dangerous, not portable, and not the way COM is designed to work.  I
> suggest you don't use it, and instead use my IFooControl method which is
> not dangerous, and portable, and as easy as accessing the C++ object
> itself.

Um... did you not say that the way suggested before was OK, and faster than
IDispatch::Invoke()?

I should also say again that I only have an IDispatch pointer to work with,
I want to get that existing control, not create a new instance.

>
> BTW, using dynamic_cast to get to the C++ object itself is no better
> than using reinterpret_cast.

But I couldn't even get it to compile - and in this case I KNEW the long was
supposed to be a pointer to the object, it was just a safety measure to use
xxx_cast<>() (which I have abandonned since, since I found the OCX wrapper
class alternative).

--
Jason Teagle
[EMAIL PROTECTED]

Reply via email to