Define a default read-size based on the devices that are connected

[bparks13]

Depending on which devices are connected, the plugin should calculate a recommended read size by summing the recommended read size for individual devices.

Recommended Read Sizes

Device	Read Size
Heartbeat	256
Neuropixels (each probe)	4096
AnalogIO	2048
DigitalIO	2048
Bno055	256
HarpSyncInput	256
MemoryMonitor	256

Implementation

The OnixDevice should contain a int getDeviceReadSize() declaration that each device then implements with the recommended value. The value should be saved as a const int deviceReadSize.

After connecting and configuring all devices, the list of devices can be iterated over, summing up the device read sizes and generating a default value for the current list of devices.

Editor Updates

Currently there is a simple text box that the user can write in to change the read size. With this update, the behavior will need to change in some way so that the user can either use the recommended value or type in their own read size depending on the results of tuning their read size.

Options:

• In other scenarios, we have added a check box to define whether the recommended value is used, or if the user wants to overwrite the value
  • There is not much room to add a checkbox, this would clutter the current editor
• Use a CallOutBox with a custom Component to create a pop-up window that can provide more context for the read size, which can include a check box or some other component to denote whether the recommend value will be used (and updated on Connect), or if the user has defined a custom read size that should remain
  • For an example, see this section in the PXI plugin, where clicking on a slot opens a pop-up to change stream names

[bparks13]

@aacuevas @jonnew In the same discussion where we suggested this implementation, we also discussed #154 where we wanted to increase the default read size to 16k, but if we are implementing this functionality should we also increase the default read size? Probably yes, so that if a user does not choose to use this dynamic read size allocation they will still benefit from a larger read size, but I wanted to confirm how these two issues would interact