Some methods are difficult to represent in an abstract/interface method. For example, setDAQ.vi uses a very specific typedef cluster that only makes sense in the specific context of our in-house Multichannel Lockin
The parent tries to be generic with a variant, I don't want a variant to be the control for the child implementation
I propose removing abstract methods from the Instrument.LockinAPI.lvclass interface class that use these types of typedef controls.
[x] setDAQ.vi
[x] setREF.vi
[x] setAO.vi
Remove (because these don't belong in the abstract class):
[x] Parse Results (all).vi
[x] Parse Results (single).vi
[x] startIVAndWait
[x] startIVsweepAndWait.vi
Update:
[x] setSweepTable.vi: make single channel and array datatype. If user needs to set more than 1 channel, call more than once
Some methods are difficult to represent in an abstract/interface method. For example,
setDAQ.vi
uses a very specific typedef cluster that only makes sense in the specific context of our in-house Multichannel LockinThe parent tries to be generic with a variant, I don't want a variant to be the control for the child implementation
I propose removing abstract methods from the Instrument.LockinAPI.lvclass interface class that use these types of typedef controls.
setDAQ.vi
setREF.vi
setAO.vi
Remove (because these don't belong in the abstract class):
Parse Results (all).vi
Parse Results (single).vi
startIVAndWait
startIVsweepAndWait.vi
Update:
setSweepTable.vi
: make single channel and array datatype. If user needs to set more than 1 channel, call more than onceMake inputs required:
setSamplingMode.vi
Fs Mode enum