This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 250816 - Codecompletion always suggest class/interface before declared instance if using camelcase expression
Summary: Codecompletion always suggest class/interface before declared instance if usi...
Status: NEW
Alias: None
Product: editor
Classification: Unclassified
Component: Completion & Templates (show other bugs)
Version: 8.1
Hardware: PC Windows 8 x64
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-02 12:52 UTC by akobberup
Modified: 2015-03-02 12:52 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments
screenshot of the default selection (23.54 KB, image/png)
2015-03-02 12:52 UTC, akobberup
Details

Note You need to log in before you can comment on or make changes to this bug.
Description akobberup 2015-03-02 12:52:50 UTC
Created attachment 152318 [details]
screenshot of the default selection

Why do codecompletion always "ignore" declared variables when looking for a suggestion, if the "normal" lookup fails, and camel case lookup is used?

For example, i have an class called TeamGroupSelection, in my method i have declared a variable of this class. The name of the variable is teamGroupSelection.
If i type "team" and invoke cc, i will get a list where my instance "teamGroupSelection" is selected.
However, if i write "tGS" and hit cc, my instance is still at the very top of the list, but it is the first matching class/interface that is found that matches the search term via camelcase. 

Wouldent it be a lot more logical that the behavior is the same if using camel case or just plain text comparison?