Hi,
I didn't get the start of this discusion, so I don't see why you need to
reload the page in the first place. You can use flags when loading the pages
(navNoReadFromCach=4, navNoWriteToCache=8) to control caching. When nothing
is selected, the document is reloaded from cache, use it in combination with
the offline property. Anyway, this is what I often use to work with the
browser ocx:
To view the source inside the WebBrowser ocx, you can do the following:
a1) Load the page;
a2) get the document property, this is a variant
a3) convert it to a MSHTML.DispHTMLDocument, using Variant To Data
a4) use the documentElement property to get the root document element
a5) use the outerHTML property to get the source code.
a6) close all the references!
Note that this is not exactlly the same as 'view source'. View source is the
code before the browser has processed it, the method above returns the
resulting html.
A better way might be to:
b1) load the url data (using WinInet Easy Get URL Bin.vi, available on
internet, Moore Good Idead site, I think).
b2) put it in the browser, by putting the html data into it. To do this,
attach a string to the Naviagte2 URL (Navigate is obsolete). The string can
be an URL, but also html, just put about: before it:
about:
chapter1
b3) when an update is needed, repeat step 2.
You can combine the methods:
c1) load it and get the data from step a1) to a6)
c2) put it in the browser using b2)
Note that this might not work, the about: method is not suitable for all
html data. E.g. links to reletive URL's are not working, because the base
URL is different!
Regards,
Wiebe.
"Scott Jordan"
wrote in message
news:506500000005000000727A0000-1021771306000@exchange.ni.com...
> The DataSocket does succeed in getting to the html for parsing, but it
> does so by downloading the whole page again. In my case, the html is
> the result of ~20 seconds of processing on the other end of the
> Internet. Downloading it a second time (after the user has browsed to
> it for viewing) is inconvenient, wasteful and basically ugly. The
> html is right there in the browser... how can I get at it?
>
> Incidentally, the Web Events.vi example is very tantalizing, but only
> two items are returned in ParamNames by the Wait On ActiveX Event.vi:
> the URL, and something called PDisp, which is just a text string
> "Microsoft Web Browser Control". Not too helpful.
>
> What's needed is something that does what the View Source menu
> selection does everyday in Internet Explorer. Near as I can tell,
> selecting View Source does not trigger any additional Internet
> activity, so that suggests it's possible to get at the html source
> without a secondary download.
>
> Any suggestions would be VERY much appreciated.
>
> Thanks in advance.