Wishlist for new Rhs2116 GUI features

[bparks13]

This will be a meta issue that keeps track of how we can implement new features and upgrade existing features for the HeadstageRhs2116 GUI.

• Once the original requested amplitude is out-of-bounds with a new amplitude step size, should the amplitude be forced to zero or should it go to the smallest amplitude with the new step size?

  • Originally spawned from this comment
  • With the changes made previously where the requested amplitude is stored, we made the decision back then to force it to zero when the step size became too large, and cap it at the highest amplitude for the given step size if the step size became too small. To be consistent, should this behavior be changed?

• Proposed changes to channel selection logic, including how parameters are copied/pasted across channels

  • Originally posted here
    • Clicking a channel should select only that channel and automatically bring up its stim parameters
    • Shift + click another channel to copy its values into current selection(s)
    • Ctrl + Click or drag box to select muliple channels and bring up the first of them in the parameter boxes. The channel the parameters belong to should be stated.
    • Shift + click another channel to copy its values into current selection(s)
  • This one will need some careful thought before we implement any changes

• Creation of basic transform nodes for manipulating stim sequence properties

  • During acquisition, we should have some method of adjusting frequency and amplitude of a given channel

[jonnew]

Related to #421