🚀 go-pugleaf

"jini" <fseconds@hotmail.com> wrote in message
news:422d9caa@newsgroups.borland.com...

> How get pOleObject, pOleDocumentSite, pOleClientSite, pCustomDoc,
> pHostUIHandler, pHostShowUI, pCustomDoc.. Etc ??

You are querying the interfaces from the wrong place.  IDocHostUIHandler,
etc, are not implemented in IHTMLWindow2.  In fact, you probably did not
carefully read what Microsoft was actually saying about IDocHostUIHandler.
You are supposed to implement **YOUR OWN** custom IDocHostUIHandler-derived
class and then give it to the browser for use.  You are not supposed to be
querying it from the browser.  Please re-read the "WebBrowser Customization"
article again.  It specifically says as much:

    "These are interfaces that you implement in your application when you
want to modify the WebBrowser Control."

That means, you have to provide your own class(es) that are derived from
IOleClientSite, IDocHostUIHandler, etc.  You obtain the browser's
IWebBrowser2 interface, not IHTMLWindow2, and then query it for IOleObject.
From there, you use IOleObject::SetClientSite() to pass the browser your own
IOleClientSite.  The browser queries the other interfaces from your own
IOleClientSite.

In the case of ICustomDoc, the browser does provide that, but again not from
IHTMLWindow2.  Using ICustomDoc, you can then pass your custom
IDocHostUIHandler-derived class to the browser via the
ICustomDoc::SetUIHandler() method.  Using IOleObject and IOleClientSite is
more flexible than using ICustomDoc, though.


Gambit