6) Nothing in the list matches exactly, so SlickEdit smartly selects the case-insenstive match,
assuming that you were saving yourself time by typing the lowercase prefix of the symbol.
Sure, we could disable this feature, but it would essentially cripple list-members because
you would have to type symbols in their exact case to find anything. Note also, if you
type a mixed case identifier, as long as the language is case-sensitive, list-members will
be case-sensitive. Basically, if you took the time to type something in upper-case (more
effort than just typing lowercase), we assume that you know what you want.
You should either provide an option for the case-sensitivity or do what visual studio does. Personally I always type things in the correct case out of habit, and having it "smartly" select the case-insensitive match is a bug for me.
As for visual studio, if it finds a case-insensitive match, it will "half-select" the match in the popup. By half-select I mean you will see a dotted rectangle surrounding the item, but it will not be highlighted. As such, it will also not work in auto complete unless you explicitly press Enter to fully select the item, then Enter again to choose it as your desired selection.
Either way, this really needs to be an option. If I'm typing code in a case sensitive language I definitely do NOT desire case-insensitive matches.