Review spikeRefractoryPeriod user interface & implementation #57
Description
A quick review of this property/functionality revealed some puzzles:
- User-set property only has impact in raster mode. Should public property be renamed to rasterSpikeRefractoryPeriod?
- There is no harm/impact to setting it in waveform mode. Should we allow it to be set? (esp. if it's renamed to rasterSpikeRefractoryPeriod)
- Current behavior is for horizontalRange(2) to override the user-set property value in spike-triggered waveform mode. Does this make sense? Any reason not to allow a shorter value?
- Current behavior appears to have no effect in stim-triggered waveform mode. Is this correct and as expected?