Bugzilla – Full Text Bug Listing
| Summary: | Property enablement broken for element properties | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Konstantin Komissarchik <konstantin> |
| Component: | Sapphire | Assignee: | Konstantin Komissarchik <konstantin> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | shenxue.zhou |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
This problem required a fix in ModelElement and GenerateImplProcessor classes. Fixed in 0.2.1 and 0.3 streams. Verified the fix using an in-house descriptor editor. |
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>