in camera view windows, in the Show menu, Auto param overlay button should be usable (and its feature usable) when there is no pupil detection ROI set
there should be no trial counter visible in status bar when there is an image recording opened
data table should not show year, month etc for each frame, but time in hours, minutes, seconds or so, just like playback control dialog
data table header rows should be coloured too (Dropped. Not possible unless we have a ustom widget with its own paint event. See Qt forums and SO for explanation.)
in example matlab codes and in streaming settings dialog, and in remote control conn dialog, the default baud should be 115200
pupil detection settings algorithm description box shows its contents squeezed. Fix that
sharpness dialog should be selectable only when it is applicable (only in case of single Basler camera)
Serial settings dialog should be renamed to Microcontroller connection settings, with refactoring as well, by renaming any "serialSettings" naming to "MCUSettings" for clarity. Also change QSettings "SerialSettings." data key names prefix for storing settings, advised substitute: "MCUSettings.COM."
in stereo camera view window, the "Camera FPS:" label should be called "Image read FPS" when a file camera is opened
in playback control dialog, the frame number and frame selector box could be unified into one row, where we keep the box, and the total number of frames only, to spare screen area
Camera calibration main window icon should be changed to something else, as the crosshair icon is the universally known icon for gaze calibration in eye-tracking related software. Crosshair icon should be reserved for use in gaze calibration related GUI elements later
make a separate static function in SupportFunctions for shortening any string for displaying in the GUI, e.g. to make C:/something/another/file.csv into C:/somethin...er/file.csv and use it in main window status bar instead of a hard coded version
make a separate static function in SupportFunctions to read out boolean values from QSettings safely, instead of the many-lines-long implementation copy past, as currently found in e.g. generalSettingsDialog
image playback control dialog can wrongly display info of the frame that only came before the one where the playback was actually paused. this is because it instantly sets its internal bools that will cancel the processing of any new incoming camera image signals. But there is no need to do that. If we remove that check at the signals entry point, the problem is fixed
graphPlot instances can wrongly display data when the playback is stopped at timepoint A, then the playback is taken elsewhere with the slider to timepoint B, and then the playback is started again: then the data between A and B will be wrongly shown as a linear line on the plot. This can be easily solved by clearing the graphPlot(s) every time a playback is started
if proc.mode is changed, dataTable and all graphPlots should be closed, as their contents are no longer valid
if main window is maximized without using the "Toggle fullscreen" button in the View menu, that button checked state is not updated. It should be
pupil detail view (a.k.a. pupil lens view in some comments) shows too small upon opening, and snaps to fit only upon window resize
please correct header description comment for connPoolCOM.h, as it contains a few mistyped sentences
automatic parametrization overlay should be visible (and its menu option checkable) even if there is no pupil detection ROI preprocessing enabled in the pupil detection settings dialog
the program does not remember the proc.mode set last time before quitting, or it overwrites it by fault upon start
upon new image recording start, recEventTracker seems to miss the first (1) trial increment and the first (blank) message entry
when switching pupil trackin on/off, camera view windows do not instantly draw the pupil detection overlay, but they should
data table header rows should be coloured too(Dropped. Not possible unless we have a ustom widget with its own paint event. See Qt forums and SO for explanation.)