You are already getting a lot of feedback on the look of your UI, so this feedback focuses on usability:
The application reads a data file. Are there any notes (file, group, or channel properties) that can be used to provide context when the data is post processed by this application?
Experiment with two scales on the Time Waveform graph. I think it would be cool and informative to see the measured strain and the computed stress on distinct y-scales on that Time Waveform graph. The application would have to take more ownership of ranging the y axes.
You should arrange configuration as close to the appropriate display as possible. For instance, Window, dB On, and Averaging Parameters apply to the FFT, so they should be close to the FFT display.
Recommend disabling configuration that is not applicable. For instance, if the user selects 'No averaging', none of the other Averaging Parameters are relevant.
Filter? what is the filter? Perhaps it would be better to turn that Boolean into a ring so that When the user selects Filter = None, they know what they are getting and when the user selects Filter = Lowpass | Highpass, they also know what is applied.
What is the relationship between stresses shown in the Stress (MPa) (P2P) numeric indicator, Peaks Found table, and FFT magnitude? The UI should reinforce concepts the user is familiar with. If a user sees numbers they cannot rationalize, they lose confidence.
Stress Level is an indicator. What are the limits before it turns yellow/orange/red? Are those limits applied to the time waveform or FFT? Be careful with just a maximum limit on stress as a broken specimen may have zero tensile stress.
Doug
Enthusiast for LabVIEW, DAQmx, and Sound and Vibration
