U
udi
Hi,
I'm writing an IE band (ATL,WTL)which enables the user navigating to
some certain links. When the user clicks a link i'm suppose to open a
new window with the chosen link. Doing most of it went quite easy -
obtaining the IWebBrowser2, using the Navigate method (with
navOpenInNewWindow + adding a needed refferer to the header) etc. On
win2K and XP everything is working just fine. But on win98 i've
encountered recurrent exceptions (access violation) in inner os
files(kernel32, browseui etc) when clicking links consecutively. It
doesn't happen every time the user clicks a link but 2 often. I've
tried wrapping my navigation code with error handling mechanism but it
doesn't get there most of the times. i've tried calling the navigation
method in a thread and wrap it in with mutex synchronization, but
exceptions r still being thrown. it seems that the navigation call
itself isn't so time and resource consuming(it returns quite fast).
The exceptions r thrown while the new explorer is being loaded. That
seems as the weakness point. I thoght it might be related to the
iexpolrer architecture(opening the new link as a new thread in the
same process) but i can't figure it out utterly.
I'm saving the choice of opening the iexplorer in a new process (if it
will work) as a last resort.
it would be very helpfull if someone could shed some light upon...
thanx,
Udi
I'm writing an IE band (ATL,WTL)which enables the user navigating to
some certain links. When the user clicks a link i'm suppose to open a
new window with the chosen link. Doing most of it went quite easy -
obtaining the IWebBrowser2, using the Navigate method (with
navOpenInNewWindow + adding a needed refferer to the header) etc. On
win2K and XP everything is working just fine. But on win98 i've
encountered recurrent exceptions (access violation) in inner os
files(kernel32, browseui etc) when clicking links consecutively. It
doesn't happen every time the user clicks a link but 2 often. I've
tried wrapping my navigation code with error handling mechanism but it
doesn't get there most of the times. i've tried calling the navigation
method in a thread and wrap it in with mutex synchronization, but
exceptions r still being thrown. it seems that the navigation call
itself isn't so time and resource consuming(it returns quite fast).
The exceptions r thrown while the new explorer is being loaded. That
seems as the weakness point. I thoght it might be related to the
iexpolrer architecture(opening the new link as a new thread in the
same process) but i can't figure it out utterly.
I'm saving the choice of opening the iexplorer in a new process (if it
will work) as a last resort.
it would be very helpfull if someone could shed some light upon...
thanx,
Udi