You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when a Scan Identifier or Peak Detector is run, while the Peak/Scan List is already open (independent whether it's currently visible or not) the Peak/Scan List is not updated. A manual press to the 'Reset Peak/Scan List' is required to visualise the Peaks/Scans in the List.
Requested behaviour would be that running an above operations will update the Peak/Scan List, ideally independent from whether it's currently visible or not. Having a GUI application, it feels counter intuitive that you have to press a reset button to obtain data. If there is no way to solve it, I suggest that 'update data' button would be a better name.
Tested on OSX, both on MSD and WSD chromatogram
Note that this is different from #913 which now works (opening/closing a chromatogram will fire an update on the Peak/Scan List).
The text was updated successfully, but these errors were encountered:
Currently, when a Scan Identifier or Peak Detector is run, while the Peak/Scan List is already open (independent whether it's currently visible or not) the Peak/Scan List is not updated. A manual press to the 'Reset Peak/Scan List' is required to visualise the Peaks/Scans in the List.
Requested behaviour would be that running an above operations will update the Peak/Scan List, ideally independent from whether it's currently visible or not. Having a GUI application, it feels counter intuitive that you have to press a reset button to obtain data. If there is no way to solve it, I suggest that 'update data' button would be a better name.
Tested on OSX, both on MSD and WSD chromatogram
Note that this is different from #913 which now works (opening/closing a chromatogram will fire an update on the Peak/Scan List).
The text was updated successfully, but these errors were encountered: