Ticket #1532 (closed: fixed)
Allow <idlist> to be defined in IDFs not only for top level components
| Reported by: | Anders Markvardsen | Owned by: | Anders Markvardsen |
|---|---|---|---|
| Priority: | major | Milestone: | Iteration 25 |
| Component: | Mantid | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Tester: | Peter Peterson |
Description
E.g. allow the following to be passed:
<component type="all-rings" >
<location />
</component>
<type name="all-rings" >
<component type="rings-front" >
<location />
</component> <component type="rings-back" >
<location />
</component>
</type>
<type name="rings-front" >
<component type="front-inner" idlist="id-front-inner">
<location z="-0.135" name="ring-front-inner" /> <!-- Tube nearest magnet body, scintillator furthest from beam -->
</component> <component type="front-middle" idlist="id-front-middle">
<location z="-0.175" name="ring-front-middle" />
</component> <component type="front-outer" idlist="id-front-outer">
<location z="-0.2855" name="ring-front-outer" />
</component>
</type>
At the moment idlist cannot be defined for nested component.
Change History
comment:3 Changed 10 years ago by Anders Markvardsen
- Status changed from new to accepted
- Component set to Mantid
comment:4 Changed 10 years ago by Anders Markvardsen
- Status changed from accepted to verify
- Resolution set to fixed
comment:5 Changed 10 years ago by Peter Peterson
- Status changed from verify to verifying
- Tester set to Peter Peterson
(In [6595]) Code for: Allow <idlist> to be defined in IDFs not only for top level components.
re #1532