Issue 755: Improved handling of ambiguous entries when importing spectral libraries that are .MSP format database dumps

issues
Status:open
Assigned To:Brian Pratt
Type:Defect
Area:Skyline
Priority:3
Milestone: 
Opened:2020-10-20 by Brian Pratt
Changed:2020-10-20 by Brian Pratt
Resolved:
Resolution:
Closed:
2020-10-20 Brian Pratt
Title»Improved handling of ambiguous entries when importing spectral libraries that are .MSP format database dumps
Assigned To»Brian Pratt
Type»Defect
Area»Skyline
Priority»3
per https://skyline.ms/announcements/home/support/thread.view?rowId=48890

We should probably pop up a dialog asking various questions as required by the import file:

------------
This file contains xxx positive-mode spectra with no declared precursor m/z value. Please select an adduct to use in positive mode m/z calculations: [list of positive adducts]
This file contains yyy negative-mode spectra with no declared precursor m/z value. Please select an adduct to use in negative mode m/z calculations: [list of negative adducts]
This file contains spectra for more than one instrument type. Please select an instrument type for import: [list of instruments found in file]
This file contains spectra for multiple tuning parameters on the the same instrument type. Please select a handling method: [Discard/Combine/Use highest spectral count]
------------