labview-dcaf / binarylogger Goto Github PK

This is admittedly not a core issue, but it's worth submitting since it involves usability.

The Historical Directory selection, if you click it, is set to look for a file. Not a directory.

Not just any file, but a tdms file.

We should set this to "Folders".

...
But, if you get to #1 first, this won't matter much.

If an RT exe is stopped by power failure the data file will be overwritten when the target reboots next time (powered up) and data is lost due to it was not moved out of the temp directory. A change to the "init" adding unique start time in file name the same way as a unique time out name is added after closing the logger will resolve this, but may defeat your original thought of moving files out of the "temp" directory. Checking if the module file already exists at init, adding uinique characters and moving it out of temp directory before creating new file might be a better option. Many autonomous systems experience multiple power outages and needs to retain their previous data when power comes back.

Refactor all editor configuration UIs to use the Table API and follow UI guidelines. Table API permits use of DataGrid controls or multicolumn listbox for channel configuration. https://github.com/LabVIEW-DCAF/Table-API

UI guidelines will be posted soon.