To do list...

[RobertHardwick]

High Priority

• [ ] General tidy up of code (remove redundant sections that have been commented out, move some functions in main.cpp into new objects).
  • perhaps move state machine, some parts of initialization, trial-table load function, and draw function into separate object such that main.cpp remains invariant?
• [x] add code for Photosensor (FTDI) checking (AW: This object is readily available.)
• [x] add code for Filter on/off option (AW: This was already built into the TrackBird object)
• [ ] Add Serial class for communication with Arduino
  • Dale has code, or we could use Asio?
• [x] Reconcile trial table file handing (use Aaron's trtable structure version)
  • Trial numbering convention starting at 1? <- NOT RECOMMENDED.
• [x] Reconcile data writing file handing (Aaron and Adrian's versions)
  • Set saved trial numbers to begin at 1 rather than 0 (re. Adrian's version)
  • (note, current code base uses Aaron's all-trials-in-one-file method, with trial numbers starting at 1.)
• [x] Integrate Adrian's new objects into main.cpp (e.g., timer), removing sections of code that become obsolete
• [x] Integraded SpeedBar object.
  • Added functionality to allow orientation to be specified, and removed dependence on Rect.
  • Merged Rect and Region2D objects.
• [x] Update necessary objects to have on/off flags, and remove drawstruc class.
• [x] Fix trakSTAR sampling problem (see separate issue)
• [x] Change HandCursor object to be a derived class rather than a nested class

  Low Priority

• [x] create textImage object to simplify displaying text onscreen (could be derived from Image? or even just added into Image itself, without needing a new object)
  • note: implemented in SDL2 version only.
• [x] Address problem where DLL files cannot be found at execution unless they exist in the Debug folder.
• [ ] Minimal examples of functionality (getting user input, drawing shapes, etc.), or is that going to be covered by main.cpp here?
• [x] Dual display - NOTE: CANNOT BE DONE IN SDL1
• [ ] Compile the calibration code into a single executable.
• [ ] See if there's a way to concurrently check/compile/load Arduino code at compile time, so that residual code from previous experiments is cleared off
• [ ] Doxygen documentation?
• [ ] Follow a style guide (eg. Google's), or come up with our own?
• [ ] Continuous integration support?
• [ ] cmake support
• [x] Consider upgrading to SDL2?
  • Advantages here, including multiple displays/windows
  • Note, there is now a new experiment version using SDL2.

[awong26]

Note, former object "Photosensor" is now renamed FTDI (since it is an FTDI usb-to-serial cable), and the relevant .h and .cpp code exists in the FTDI folder along with the relevant library. Additionally, this object can be used for just general purpose digital i/o (up to 4 channels), such as for TMS triggering.

This is to distinguish it from the Arduino code that Alex is working on, which will have a separate photosensor.

[adrianhaith]

I propose we maintain Aaron's trial/target table handling. It makes more sense to have an array of structures than an object. Key thing is to keep experiment-specific stuff all within main.cpp. All other stuff should be generic and not need to change for each new experiment. Or at least change by adding functionality, not changing it.

For displaying objects, I think replacing the "drawstruc" with flags stored inside the objects themselves makes sense as it reduces the amount of extraneous code and improves readability.

[awong26]

In that case, it will be necessary to embed flags in all the other objects to be drawn, i.e., image/object2D, path2D, and region2D.