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

Bug 313700

Summary:	What's New page -> Platform -> Compare Editor -> Open Type
Product:	[Eclipse Project] Platform	Reporter:	Nayna Jain <jainnayna>
Component:	Doc	Assignee:	Platform-Doc-Inbox <platform-doc-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert
Version:	3.5.2
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Nayna Jain

2010-05-20 07:26:47 EDT

Build Identifier: Eclipse 3.5.2

In Eclipse 3.5.2 ,I was accessing the following link.
Eclipse Help -> Help Contents -> Workbench User Guide -> What's New -> Platform Changes -> Compare Editor enhancments.

In this it is mentioned that " The current text selection will be used to popoulate the filter field of the Open Type and Open Resource Dialogs".

The above mentioned features works fine for Open Resource but not for Open Type. In case my case, "Open Type" didn't work both for JDT and CDT. Also, my understanding is that any change specified in the "Platform Changes" section, or "Workbench Changes" section, it should work both in JDT/CDT. Is this correct understanding. ?





Reproducible: Always

Comment 1 Dani Megert

2010-05-20 07:55:27 EDT

This work works fine for me using 3.5.2 and the Text or Java compare editor. Can't speak for CDT since I don't know whether they offer their own compare editor. Note that Open Type only sets the filter if the string makes sense for a type.

Comment 2 Nayna Jain

2010-05-20 08:09:12 EDT

This feature is mentioned in "New Features in Platform and Equinox Section". From Eclipse Help Manual, we get it in Help -> Workbench User's Guide -> What's New. So, aren't these changes supposed to work for both JDT/CDT. Otherwise, shouldn't they be specified in "What's New in JDT" Section.

Comment 3 John Arthorne

2010-05-20 08:56:07 EDT

(In reply to comment #0)
> Also, my
> understanding is that any change specified in the "Platform Changes" section,
> or "Workbench Changes" section, it should work both in JDT/CDT. Is this correct
> understanding. ?

Not necessarily. Sometimes platform provides new API, and other projects such as CDT have to adopt that new API before they get the new functionality. Sometimes new features aren't turned on automatically for compatibility reasons. I suggest entering a bug against CDT requesting that this feature be enabled in their tools.