Mindaugas Kavaliauskas wrote:
That's why I simplified code and used FindConnectionPoint().
Does this from MSDN help explain:
===
This is all well and good again, but begs another question: "How does a client
know the IID it wants to connect to?" Excellent question! There are two possible
answers:
The client assumes that the object supports a connection point for an interface
known at compile time. For example, control containers assume that controls
support the IPropertyNotifySink interface as an outgoing interface, and can pass
IID_IPropertyNotifySink directly to FindConnectionPoint (as we'll see in the
"Properties" section).
The client uses the object's type information to find the IID of an outgoing
dispinterface. A control provides the IID of its event set in this fashion.
The first answer is easy to work with—it's like passing an IID to
QueryInterface. The second is a little trickier, because as a client you need a
mechanism to look for the IID you want, without having to load the object's type
library from its DLL or EXE. That mechanism is exactly what the
IProvideClassInfo interface was created for, as described earlier under
"Automation Extensions." The ITypeInfo interface returned from
IProvideClassInfo::GetClassInfo is the interface on the object's entire type
library. With this pointer you can call ITypeInfo::GetTypeAttr to look for an
interface with the Source attributes and call GetRefTypeOfImplType and
GetRefTypeInfo to retrieve the ITypeInfo interface for that particular
interface. Outgoing interfaces can be standard COM type interfaces or
dispinterfaces. Only one, however, can be marked with the Default attribute that
makes it the primary “event set.”
===
To find out the events, I look in the type library, whereas someone "lucky"
enough to be using VB would get the info via ITypeInfo etc. See below:
Regards
Alex
From OLE View bundled with VB6:
[
uuid(F41DF7FB-5014-4859-B4DD-854A9D2143CC),
version(1.17),
helpstring("Events interface for CoBpTi Object")
]
dispinterface ICoBpTiEvents {
properties:
methods:
[id(0x00000001)]
HRESULT terminalDspEvent(
[in] BSTR* row1,
[in] BSTR* row2,
[in] BSTR* row3,
[in] BSTR* row4);
[id(0x00000002)]
HRESULT infoEvent([in] BSTR* text);
[id(0x00000003)]
HRESULT exceptionEvent(
[in] BSTR* text,
[in] long code);
[id(0x00000004)]
HRESULT txnResultEvent(
[in] long txnType,
[in] long resultCode,
[in] BSTR* text);
[id(0x00000005)]
HRESULT referralEvent([in] BSTR* text);
[id(0x00000006)]
HRESULT lppCmdFailedEvent(
[in] long cmd,
[in] long code,
[in] BSTR* text);
[id(0x00000007)]
HRESULT cardDataEvent(
[in] BSTR* text,
[in] BSTR* cardNo,
[in] BSTR* expDate,
[in] BSTR* track2);
[id(0x00000008)]
HRESULT resultDataEvent(
[in] long resultType,
[in] long item,
[in] BSTR* description,
[in] BSTR* Value);
[id(0x00000009)]
HRESULT terminatedEvent(
[in] BSTR* reason,
[in] long reasonCode);
[id(0x0000000a)]
HRESULT statusChangeEvent([in] long newStatus);
};
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
