387126 – [open type] Open Type should prioritize exact matches over camel-case matches

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 387126 - [open type] Open Type should prioritize exact matches over camel-case matches

Summary: [open type] Open Type should prioritize exact matches over camel-case matches

Status:	CLOSED DUPLICATE of bug 109670

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	4.2
Hardware:	All All

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	JDT-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:	360468
Blocks:
	Show dependency tree

Reported:	2012-08-13 11:57 EDT by Brian de Alwis
Modified:	2016-05-19 10:50 EDT (History)
CC List:	5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Brian de Alwis

2012-08-13 11:57:31 EDT

When programming for E4, I frequently use Open Type to bring up the various E4 model interface definitions, like MPart.  But the Open Type dialog gives precedence to matches using camel-casing over the exact type names.  For example, MPart shows:

   ManifestPartitionScanner
   MaximizePartHandler
   MinimizePartHandler
   MockPart
   MockPartListener
   ModelParticipantAction
   ModelParticipantMergeOperation
   MoveParticipant
   MPart
   MPartDescriptor

This was previously reported and fixed in bug 170885, but the behaviour seems to have been resurrected.

Comment 1 Dani Megert

2012-08-14 03:59:47 EDT


*** This bug has been marked as a duplicate of bug 360468 ***

Comment 2 Markus Keller

2015-10-30 08:53:13 EDT

*** Bug 394919 has been marked as a duplicate of this bug. ***

Comment 3 Markus Keller

2015-10-30 08:55:20 EDT

It's not clear if bug 360468 will solve this for free. Keeping this bug open in JDT.

Comment 4 Markus Keller

2015-10-30 08:55:51 EDT

Tentatively targeting 4.6

Comment 5 Dani Megert

2016-05-19 10:50:06 EDT


*** This bug has been marked as a duplicate of bug 109670 ***