Browser Control Events ?

  • Thread starter Thread starter meh
  • Start date Start date
M

meh

What are the best events to hide and unhide the progressbar when navigating
to web pages using the AxWebBrowser control. I have tried a couple of
events i.e. BeforeNavigate2 to set the pbar.visible to True and the
DocumentComplete to set pBar.Visible to False but none seem to function the
way I would like them to. If I leave pBar.Visible = True the pBar seems to
be working just fine, but if I try to hide it when its not in use I dont get
to see it work. Any suggestions???





tia
meh
 
Hi Meh,

Navigate2 to start is fine,

A webpage can exist in a lot of documents (frames) and therefore the first
documentcomplete says nothing (with framepages that is mostly a very small
document)

A webpage is ready (if it is well done by the makers) if the
navigatecomplete2 fires.

But if there are crazy pages between it can give a lot of strange
situations.

I hope this helps?

Cor
 
thx Cor

meh

Cor said:
Hi Meh,

Navigate2 to start is fine,

A webpage can exist in a lot of documents (frames) and therefore the first
documentcomplete says nothing (with framepages that is mostly a very small
document)

A webpage is ready (if it is well done by the makers) if the
navigatecomplete2 fires.

But if there are crazy pages between it can give a lot of strange
situations.

I hope this helps?

Cor
Click to expand...
 
In my experience, Navigate2 is not generally reliable. It works
some/much of the time, but not always. Neither is DocumentComplete.
The best technique I've found is to check the dispatch object on
DocumentComplete = IE main window. Note that even this fails for
pages that have active control of their rendering fired by the frame's
onload event. There is a note in the KB (unfortunately I've lost
track of it, but look for pDisp and DocumentComplete) that is helpful.

Regards
 
Hi Guys;

Because I'm using the browser control on a child of a MDI app the thing
thats giving me the best results right now is the
OnLostFocus

event of the child. This seems to work the best for this app. It still is
not exacly what I was looking for but it works.

Thanks for all the great ideas......

meh
 
Back
Top