Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 337489 - Property enablement broken for element properties
Summary: Property enablement broken for element properties
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Sapphire (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Konstantin Komissarchik CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-17 16:09 EST by Konstantin Komissarchik CLA
Modified: 2021-11-19 09:21 EST (History)
1 user (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 Konstantin Komissarchik CLA 2011-02-17 16:09:31 EST 
The IModelElement.isPropertyEnabled( [prop] ) stopped working for element properties. The problems can manifest in a number of ways. I have encountered this when investigating why a content outline node that was set to hide on disabled state of its property wasn't properly hiding/showing.

In the following example FastSwapSettings is an element property whose enablement is controlled by a condition in the model. 

<node>
  <property>FastSwapSettings</property>
  <label>FastSwap</label>
  <hint><name>hide.if.disabled</name><value>true</value></hint>
  <section>
    <content>
      ...
    </content>
  </section>
</node>
Comment 1 Konstantin Komissarchik CLA 2011-02-17 16:11:29 EST 
This problem required a fix in ModelElement and GenerateImplProcessor classes.
Comment 2 Konstantin Komissarchik CLA 2011-02-17 19:09:11 EST 
Fixed in 0.2.1 and 0.3 streams.
Comment 3 Shenxue Zhou CLA 2011-02-25 11:54:33 EST 
Verified the fix using an in-house descriptor editor.