As a user I think it would make sense to lay macros out differently at times. A couple of examples of this:
Currently in the MCLEN IOC, we have axis parameters shown as a big list of macros (ie. VELO1 for AXIS1, VELO2 for AXIS2 etc.) - we could lay these out like (if axis1 == yes) then show options for axis1 etc.
Some devices can talk both IP and serial. For IP this is easy, in most cases we just need an IP address and occasionally a port. Serial however may need baud rate, parity, bits, flow control and so on - for this we should maybe have one macro that selects between the two and show in the GUI the appropriate settings depending on what's been selected.
Needle valve - the needle valve is some extra functionality that the eurotherm uses, depending on whether the NEEDLE_VALVE macro is set to yes - if this is the case we should show the needle valve options (these are not currently in config.xml as the list in the GUI would get huge especially if not using)
Acceptance criteria
[ ] One IOC (mclen easiest?) config.xml is modified to form a hierarchy system as suggested above
[ ] the GUI is modified to accept these in a suitable way, ie a treeview where if axis1 == yes but axis2 == no then axis1's items are expanded but axis2's are collapsed.
[ ] IOCs are examined and additional tickets are created for other IOCs that may benefit from this system
As a user I think it would make sense to lay macros out differently at times. A couple of examples of this:
yes- if this is the case we should show the needle valve options (these are not currently in config.xml as the list in the GUI would get huge especially if not using)Acceptance criteria