Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 357871 - MEEnumControl should respect literal translation
Summary: MEEnumControl should respect literal translation
Status: CLOSED FIXED
Alias: None
Product: ECP
Classification: Modeling
Component: Editor (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 0.8.9   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-15 15:42 EDT by Nikolay Kasyanov CLA
Modified: 2012-05-07 10:38 EDT (History)
2 users (show)

See Also:


Attachments
proposed patch (1.36 KB, patch)
2011-09-15 15:44 EDT, Nikolay Kasyanov CLA
eclipse: iplog+
Details | Diff
fixed patch, with some javadoc fix (3.19 KB, patch)
2011-09-16 06:57 EDT, Nikolay Kasyanov CLA
eclipse: iplog+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolay Kasyanov CLA 2011-09-15 15:42:05 EDT
Build Identifier: M20110909-1335

It should not simply use get enum literal's "literal"  property, but should  use label provider to receive literal translation from model's edit plugin plugin.properties file

Reproducible: Always

Steps to Reproduce:
1. Edit some enum literal translation in plugin.properties of your model's edit plugin
2. Start ECP base app
3. See no changes in enum literal names in MEEnumControl
Comment 1 Nikolay Kasyanov CLA 2011-09-15 15:44:02 EDT
Created attachment 203448 [details]
proposed patch
Comment 2 Nikolay Kasyanov CLA 2011-09-16 05:41:58 EDT
ooops, looks like it brokes control entirely
Comment 3 Nikolay Kasyanov CLA 2011-09-16 06:57:02 EDT
Created attachment 203482 [details]
fixed patch, with some javadoc fix

Works now.
Had to use ComboViewer against simple Combo, because Combo provides only string values for data binding, which unsuitable for enum use case
Comment 4 Jonas Helming CLA 2011-09-19 11:03:38 EDT
resolved in master