C
Clint MacDonald
I have used the AxWebBrowser in a Visual Basic Project...with some success
but some buggy things...
I found that both Framework 1.0 and 1.1 had to be installed for it to work
properly.
Navigating using the OnActivate envent works,, using the onLoad or onEnter
events do not...If I make a button that navigates to a fil/page, then it
works fine....
however, here are a few more things I have noticed....in my MDI environment,
1) if I have another child opn that has a datagrid on it, the child is
maximized and the datagrid is resized using anchors as a result, then when
the new child is opened with the AxWebBrowser on it, it causes all sorts of
problems....
2) if the previous child window is not maximized or the datagrid has fixed
width, the child window with the AxWebBrowser on it loads fine with the
OnActivated event navigating....
3) If the other current child window does not have a datagrid on it, the
AxWebBrowser loads fine
4) If a previous child window with a datagrid, maximized is open, and then
another window without a datagrid on it is opened and maximized, then
AxWebBrowser window opens fine...thus meaning that it does not work fine
when the previous current child window has a datagrid on it, is maximized,
and the datagrid is resized using the anchors....
I do not see the link here, but there is a definate pattern that is now
obvious and predictable.
any ideas...
Clint
but some buggy things...
I found that both Framework 1.0 and 1.1 had to be installed for it to work
properly.
Navigating using the OnActivate envent works,, using the onLoad or onEnter
events do not...If I make a button that navigates to a fil/page, then it
works fine....
however, here are a few more things I have noticed....in my MDI environment,
1) if I have another child opn that has a datagrid on it, the child is
maximized and the datagrid is resized using anchors as a result, then when
the new child is opened with the AxWebBrowser on it, it causes all sorts of
problems....
2) if the previous child window is not maximized or the datagrid has fixed
width, the child window with the AxWebBrowser on it loads fine with the
OnActivated event navigating....
3) If the other current child window does not have a datagrid on it, the
AxWebBrowser loads fine
4) If a previous child window with a datagrid, maximized is open, and then
another window without a datagrid on it is opened and maximized, then
AxWebBrowser window opens fine...thus meaning that it does not work fine
when the previous current child window has a datagrid on it, is maximized,
and the datagrid is resized using the anchors....
I do not see the link here, but there is a definate pattern that is now
obvious and predictable.
any ideas...
Clint