wow..
thanks so much for the idea. yahhh it is a lame work-around, but it works anyhow. i don't know if there are rules against stupid code. but i tried eveything i could find. spent an entire weekend looking for it. no other solution worked. =(
so here, i sent the mouse event to the CAxWindow after Navigate() and there was no longer a need to click with the mouse. keyboard works then.
Code:
m_HostWnd.SendMessageToDescendants(WM_LBUTTONDOWN, 0, NULL);
/* m_HostWnd is CAxWindow, i just placed NULL at the last part, i think it's supposed to be the mouse position.. */
thanks
i also used keybd_event... thanks
Code:
switch(scrollType)
{
case StepDown:
keybd_event(VK_DOWN, 0xD0, 0,0);
Sleep(100);
keybd_event(VK_DOWN, 0xD0, KEYEVENTF_KEYUP,0);
break;
case StepUp:
keybd_event(VK_UP, 0xC8, 0,0);
Sleep(100);
keybd_event(VK_UP, 0xC8, KEYEVENTF_KEYUP,0);
break;
case PageDown:
keybd_event(VK_NEXT, 0xD1, 0,0);
Sleep(100);
keybd_event(VK_NEXT, 0xD1, KEYEVENTF_KEYUP,0);
break;
case PageUp:
keybd_event(VK_PRIOR, 0xC9, 0,0);
Sleep(100);
keybd_event(VK_PRIOR, 0xC9, KEYEVENTF_KEYUP,0);
break;
case ScrollBottom:
keybd_event(VK_END, 0xCF, 0,0);
Sleep(100);
keybd_event(VK_END, 0xCF, KEYEVENTF_KEYUP,0);
break;
case ScrollTop:
keybd_event(VK_HOME, 0xC7, 0,0);
Sleep(100);
keybd_event(VK_HOME, 0xC7, KEYEVENTF_KEYUP,0);
break;
}