To reproduce the strange behavior:
1. Open the auto complete list in an empty line.

2. Type a character which is NOT in the list. As result NOTHING is highlighed in the list.

3. Close the autocomplete window (but NOT with the keyboard, but e.g. by clicking somewhere in the view)

So "m_bHighLight" is FALSE from the action in 2.
The NEXT time you open the auto complete window (with ...::Show) NOTHING is highlighted in the begining.

 

Now when you do it different:
1. Open the auto complete list in an empty line.

 

There's a small bug in autocomplete window.

The function "CXTPSyntaxEditAutoCompleteWnd::Show"

does NOT set the member variable "m_bHighLight".

This means it's random whether the first line of the list in auto-complete-window

is selected when opening the list or not. (Actually it depends how the auto-complete-window

was closed the previous time: With a selection because the last typed character was for

a string in the list or not).

What makes it even more random is the fact, that the member variable "m_bHighLight"

is NOT initialized at all in the constructor of "CXTPSyntaxEditAutoCompleteWnd".

(So the very first time it's totally random and can be e.g. different in Debug and Release).

 

Here my proposal for a bug fix in file "XTPSyntaxEditAutoCompleteWnd.cpp"

in function "CXTPSyntaxEditAutoCompleteWnd::Show" ca. in line 143:

 

Replace:

 

    ...

    int nSearch = Search(strSearch);
    m_nHighLightLine = nSearch;

    ScrollTo(nSearch);
    ...

 

with

 

    ...

 

Best regards

 

P.S.:

I really don't know how the people could use the ActiveX variant without the possibility

to inspect/modify the source code...
I just want to make a proposal for the following effect (what - I think - is a bug).