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

Bug 384058

Summary: Difference in constants in GEFMessages between 3.5 and 3.7
Product: [Tools] GEF Reporter: Aleksandr Kravets <aleksandr.kravets>
Component: GEF-Legacy GEF (MVC)Assignee: gef-inbox <gef-inbox>
Status: RESOLVED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: nyssen
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Aleksandr Kravets CLA 2012-07-02 11:21:11 EDT
Build Identifier: M20120208-0800

I am using GEF in my product based on Eclipse 3.5. I moving to 3.7 and all code compiles fine, except my MarqueeToolEntry that uses messages from GEFMessages that are not in GEF 3.7: GEFMessages.MarqueeTool_Desc, GEFMessages.MarqueeTool_Connections_Desc and GEFMessages.MarqueeTool_Nodes_Desc. Is there a reason these were not included in 3.7?

Reproducible: Always
Comment 1 Alexander Nyßen CLA 2012-07-02 11:53:19 EDT
Yes, in the 3.7 release timeframe, MarqueeToolEntry was refactored to offer new behavioral modes (see http://wiki.eclipse.org/GEF/New_and_Noteworthy/3.7 or bug #185960 for details). GEFMessages was changed in this turn to offer proper description texts for the now supported modes:

public static String MarqueeTool_Connections_Touched_Desc;
public static String MarqueeTool_Connections_Contained_Desc;
public static String MarqueeTool_Nodes_Touched_Desc;
public static String MarqueeTool_Nodes_Contained_Desc;
public static String MarqueeTool_Nodes_Touched_And_Related_Connections_Desc;
public static String MarqueeTool_Nodes_Contained_And_Related_Connections_Desc;

As the class is internal, you may not rely on it. However, I think you should be able to easily adopt your code to the new messages listed above. Resolving as wontfix.
Comment 2 Aleksandr Kravets CLA 2012-07-02 11:58:13 EDT
Correct, I just wanted to find out why it was merged. Thanks.
Comment 3 Aleksandr Kravets CLA 2012-07-02 13:02:25 EDT
(In reply to comment #2)
> Correct, I just wanted to find out why it was merged. Thanks.

Sorry, not merged.