Mayayana
2/27/2011 10:16:00 PM
This one's solved. I fixed it either by changing
the IE instance to a ShellBrowserWindow (same
thing, different CLSID) or by removing the extra
parameters to Navigate. I'm not sure which.
This might be worth noting for anyone who uses
Shell operations. The whole thing is generally the
same in Vista/7, but as with so many other things,
MS broke a few odds and ends.
| I've asked about this in the Shell group but
| that group doesn't get much traffic anymore.
|
| I wrote an Explorer Bar, some time ago, that
| I've used in Win9x and XP. Recently I've been
| testing it out in Win7. The bar is loaded by a
| BHO, which is passed a pointer to the pseudo-IE
| instance that represents the folder window. In the
| past I've been able to then use IE.Navigate from within
| the Explorer Bar to change the location displayed
| in the folder window. (What the Navigation Pane
| now provides in Win7.) In Win7 the Navigate method
| now produces "unspecified error". I can't find any
| docs about what's changed in Win7 for shell
| extensions. I know that I have the IE instance
| because I get access to the ShellFolderView of the
| folder via IE.Document, but the nature of the pseudo-IE
| folder object seems to have changed.
|
| Does anyone here know what I'm talking about and
| know what's changed? (The pseudo-IE I'm referring to
| is the same object returned in a Shell.Windows collection.
| It's not really an IE instance. That was just a scam that
| came out of the Netscape lawsuit, which spawned the
| Active Desktop nonsense and "webbified" folders. But
| programmatically it's an IE instance, and it acts like
| one in many ways, for the sake of backward compatibility.)
|
|