We understand it has delays :( But global webbrowser is not solution.

For 12.0 release we're working with own Markup to replace WebBrowser's rendering.

Hmm, I tried setting the tooltip via CMyRecordItem::SetTooltip (once in the constructor). I still get high CPU-peaks.

 

No, this is indeed a bug or "bad" implementation (I know this is hard stuff).

 

Take a look at CHTMLToolTip::GetToolSize:

 

READYSTATE rs;

do
{
    AfxGetApp()->PumpMessage();
    m_pBrowserApp->get_ReadyState (&rs);
}

while (rs != READYSTATE_COMPLETE);

 

And later you call this a lot of times:

m_wndBrowser.MoveWindow(0, 0, cx, nScrollHeight);

 

An idea is to instantiate one browser object only (Navigate to "about:" only once!), which you use whenever a tooltip should be displayed. Remember that the Navigate-method takes some 100+ milliseconds on some systems!

 

The size of the html-window is always a problem. I think I have an idea for that too. Simply make it the size of the screen, and then you put all html-code inside a <table width="preferredWidth"> and then you show a window with this browser as a child and set the desired dimensions of the parent window - not the browser itself!

 

Perhaps the resizing of the browser is not the bottleneck here, but if it turns out to be slow you know how to fix it :).

 

Override INT_PTR CXTPReportControl::OnToolHitTest(CPoint point, TOOLINFO* pTI) const method instead

or don't override any method, call GetToolTipContext()->SetStyle(xtpToolTipHTML);  and set HTML tooltip using pItem->SetTooltip("<b>test</b>");

I also hit the same problem.

Oleg, a small sample would be nice!

 

Then I override:

const XTP_NM_REPORTTOOLTIPINFO& CMyReportControl::OnGetToolTipInfo(CXTPReportRow* pRow, CXTPReportRecordItem* pItem, CString& rstrToolTipText)

{

   ...

}

 

What am I doing wrong?

don't use FillInToolInfo but set LPSTR_TEXTCALLBACK.

 

Yes, LPSTR_TEXTCALLBACK is supported.

 

lpszText  = LPSTR_TEXTCALLBACK;

This seems very wasteful, as it is building the tooltip text for pretty much every mouse message. I put it in to my application and just by moving the cursor around on the view it uses a lot of CPU (about 40% on 3.2GHz P4D), and no tooltips are even displayed.

 

Is there a way to use these tooltips, by only having to generate the HTML when the tooltip is displayed (like when using LPSTR_TEXTCALLBACK in OnToolHitTest) rather than after every mouse message?

 

Thanks,

Graham