User forums > Nightly builds

The 06 March 2011 build (7040) is out.

<< < (4/8) > >>

Cubic:
Another thing I noticed: This doesn't happen the first time code completition kicks in - the first time everything works fine, it is only after you deleted a -first- comma for the first time (while the tip is being shown) it starts behaving weird.

ollydbg:
If I revert the change in rev 6997 around the line 1888 in nativeparser

revert to:

--- Code: ---            if (token->GetFormattedArgs() != _T("()"))
            {
                wxString s;
                BreakUpInLines(s, token->GetFormattedArgs(), chars_per_line);
                m_CallTips.Add(s);
            }
            else if (token->m_TokenKind == tkTypedef && token->m_ActualType.Contains(_T("(")))
                m_CallTips.Add(token->m_ActualType);

--- End code ---

then, the highlight in call tip works fine.  :D

killerbot:
could you commit this ? Then we can include it in this weekends nightly build.

ollydbg:

--- Quote from: killerbot on April 02, 2011, 07:52:18 am ---could you commit this ? Then we can include it in this weekends nightly build.

--- End quote ---
?me? or other guy??? :?

PS:
forget to mention there is a patch to avoid a recursive class hierarchy search which can avoid the crash of CC.

MortenMacFly:

--- Quote from: killerbot on April 02, 2011, 07:52:18 am ---could you commit this ?

--- End quote ---
Please don't. This would disable the pretty print of tokens and (even worse) would leave unused code stubs.

I think oBFusCATed should look into it. He provided the pretty print part and I believe with the research done by ollydbg he might be able to fix this in a way that we can keep the pretty printing (I am personally quite used to it meanwhile).

Navigation

[0] Message Index

[#] Next page

[*] Previous page