The "open type" dialog returns results that are less than desirable, and basically violates the camel case matching. This is likely a result of #2420 or the multiple issues that were successively solved following that enhancement.
I usually use Camel Case along with lower case letters to narrow down the search to the types I'm looking for. The current behavior of "open types" ignores the case when using this method, voiding the point of camel case search.
For example, this is what searching for "ArrL" would return in previous versions (up to 4.38 I assume, but I haven't tested all of them) :
This is what we want and the ArrayList is easy to find.
Test the same with 4.40 and you will get this instead :
About 75 results, and I had to scroll down through a fair bit of completely unrelated "matches" due to erroneous case handling.
The "open type" dialog returns results that are less than desirable, and basically violates the camel case matching. This is likely a result of #2420 or the multiple issues that were successively solved following that enhancement.
I usually use Camel Case along with lower case letters to narrow down the search to the types I'm looking for. The current behavior of "open types" ignores the case when using this method, voiding the point of camel case search.
For example, this is what searching for "ArrL" would return in previous versions (up to 4.38 I assume, but I haven't tested all of them) :
This is what we want and the ArrayList is easy to find.
Test the same with 4.40 and you will get this instead :
About 75 results, and I had to scroll down through a fair bit of completely unrelated "matches" due to erroneous case handling.