I looked at Slimbrowsers website for support (http://www.flashpeak.com
) and came across this posting. Hopefully your program could comply with these design specs and still function correctly/fully???
This page is for IE toolbar vendors/developers who also wish to have your toolbars compatible with SlimBrowser.
The main difference between IE and SlimBrowser is that SlimBrowser is a MDI (Multiple-Document Interface) application while IE is a SDI (Single-Document Interface) application. The key point is to make your toolbar interact efficiently and correctly with SlimBrowser under a MDI environment.
To make your toolbar compatible with SlimBrowser, the following points should be noticed:
Expect a new site interface pointer when the user switches from one site window to another.
The site pointer is is passed by way of IObjectWithSite::SetSite(IUnknow *pSite). Be prepared to release your current site pointer and replace it with a new one. You should update your toolbar button status correctly based on the new site pointer. (As a point to note, Google toolbar doesn't update its page rank indicator correctly when the user switches to another site in SlimBrowser.) Only have the toolbar destroy itself when a NULL pointer is set, which indicates the browser is quitting. The common flaw of many IE toolbars is that it doesn't expect a second new site pointer or won't process it correctly. For such kind of toolbars, SlimBrowser have to recreate the entire toolbar when the user switches between site windows. That'll cause bad drawing glitches which is a great distaste to users.
Avoid using methods and objects supported by Internet Explorer object but not supported by standard Web Browser control
For example, ShowBrowserBar is not supported by Web Browser Control. If you call this method, it will simply be ignored.