| 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
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. Correct, I just wanted to find out why it was merged. Thanks. (In reply to comment #2) > Correct, I just wanted to find out why it was merged. Thanks. Sorry, not merged. |