Bugzilla – Full Text Bug Listing
| Summary: | Camel case matches not work when "::" as trigger | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Tools] CDT | Reporter: | Loaden <loaden> | ||||
| Component: | cdt-core | Assignee: | Project Inbox <cdt-core-inbox> | ||||
| Status: | NEW --- | QA Contact: | Jonah Graham <jonah> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cdtdoug, jens.elmenthaler, loaden, yevshif | ||||
| Version: | 8.0 | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 192887 [details]
Screenshot for this issue
Do you mean by 'Camel case matches will not work'? Is it that the order of the proposals is unexpected? (In reply to comment #2) > Do you mean by 'Camel case matches will not work'? Is it that the order of the > proposals is unexpected? Not only the order of questions, but the algorithm fails to match. (In reply to comment #3) > Not only the order of questions, but the algorithm fails to match. Please explain that to me: What are the proposals you are seeing, what are the ones you would expect instead? (In reply to comment #4) > (In reply to comment #3) > > Not only the order of questions, but the algorithm fails to match. > Please explain that to me: What are the proposals you are seeing, what are the > ones you would expect instead? Please see the attachment of Screenshot: https://bugs.eclipse.org/bugs/attachment.cgi?id=192887 When I typing: ATL:CWindow It's should proposals CWindow, but not CAxWindow, That's right? You can test this issue use the demo: namespace ATL { class CAxWindow {}; class CAxWindowEx {}; class CWindow {}; } ATL::CWin | // type here Sorry for my poor english. I understand, I raised the same concern about the implementation in bug 173458, however this is done on purpose. (In reply to comment #5) > (In reply to comment #4) > > (In reply to comment #3) > > > Not only the order of questions, but the algorithm fails to match. > > Please explain that to me: What are the proposals you are seeing, what are the > > ones you would expect instead? > Please see the attachment of Screenshot: > https://bugs.eclipse.org/bugs/attachment.cgi?id=192887 > When I typing: > ATL:CWindow > It's should proposals CWindow, but not CAxWindow, That's right? I really consider this a feature:-), which is that you don't have to specify all the segments, but can leave out some in between. It frequently annoys me in the JDT, for example. But there is a certain cost you have to pay, maybe the ordering should be tweaked. |
Build Identifier: I20110310-1119 Hi, CDT Term! Nice to see the new feature "Show camel case matches" has enabled. I found a bug is this feature. --- namespace ATL { class CAxWindow {}; class CAxWindowEx {}; class CWindow {}; } ATL:: // Issue occured here --- If auto activation using "::" trigger, Camel case matches will not work. And this code: ---class CAxWindow {}; class CAxWindowEx {}; class CWindow {}; ::CWi // Issue occured here CWi // Works well -- If using "::" as trigger, Camel case matches not work too. Reproducible: Always