| Summary: | [diagram] Image specification for diagram parts inconsistent with the rest of sdef | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Konstantin Komissarchik <konstantin> |
| Component: | Sapphire | Assignee: | Ling Hao <ling.hao> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | gregory.amerson, ling.hao, shenxue.zhou |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Konstantin Komissarchik
Setting the target to 0.3 as this will be a significant language change, it would be good to do that before shipping the 0.3 release. If this proves to be impossible with Graphiti in the way, we can defer this to the 0.4 release to be done concurrently with removing Graphiti dependency. Bulk deferral of diagram-related items to the 0.5 release. Image specifications are now consistent with the rest of the sdef. Question regarding this change. Before we could use expressions in the <id> element to resolve which image to load. How do we get this same feature now? OK, answered my own question by just looking at IDiagramNodeImageDef I can just now return use an expression in the <path> element. Verified the fix. Closing. Referencing Comment #3, am I correct in assuming that this was fixed by Ling. If so, the Assigned To field should be updated accordingly. If not, someone else besides Shenxue will need to perform the verification. (In reply to comment #7) > Referencing Comment #3, am I correct in assuming that this was fixed by Ling. > If so, the Assigned To field should be updated accordingly. If not, someone > else besides Shenxue will need to perform the verification. Yes it's fixed by Ling. I wasn't paying attention to the assigned to field. Fixed now. |