Martijn Laan

Thanks! Also thanks for releasing 5.5.1.

I've looked at implementing it as an element colour but am unsure how to do this properly.

I've updated the patch to use the suggested names.

Would be great to have this.

Correct, no lexer is involved.

Have you looked at ScintillaBase::AutoCompleteStart? It takes the minimum sizes (AutoComplete's own minimum of 100 pixels and the listbox's desired width as returned by GetDesiredRect (which is 15,6 times the average char width on Win32 as returned by ListBoxX::MinClientWidth)) and calculates the final minimum size but taking the maximum. In the same place it handles the maximum size set by SCI_AUTOCSETMAXWIDTH. So I'm pretty sure that this is the correct place to handle a third minimum size set...

Have you looked at ScintillaBase::AutoCompleteStart? It takes the minimum sizes (AutoComplete's own minimum of 100 pixels and the listbox's desired width as returned by GetDesiredRect (which is 15,6 times the average char width on Win32 as returned by ListBoxX::MinClientWidth)) and calculates the final minimum size but taking the maximum. In the same place it handles the maximum size set by SCI_AUTOCSETMAXWIDTH. So I'm pretty sure that this is the correct place to handle a third minimum size set...

FYI, in the meantime I think I've noticed a similar situation in SciTEBase::CharAddedinside the else if (wEditor.AutoCActive()) bit: here it does braceCount++ before calling StartCallTip();. This causes a problem if earlier some calltip was canceled which leaves braceCount at some number which has become meaningless. Not sure what the fix would be, I think it's incrementing instead of setting to 1 to handle the case when the user is manually switching between autocomplete and calltips while entering...