|Title||»||Usability idea: when we fail to open a Skyline document, check to see if it actually IS a Skyline document|
|Assigned To||Guest||»||Brian Pratt|
Lately we seem to get a lot of support requests where users are trying to just fire up Skyline then open a mass spec raw file. We issue an error like "the file contains an error at line 1 column 1", which only makes sense if the file is actually XML data.
Instead, we should:
scan the first few hundred bytes to see if it contains "srm_settings" and "Skyline"
if so, then throw that line/column error, fine.
if not, see if we can identify it as mass spec data.
if it is mass spec data, suggest they use File > Import Results, or if they don't have any targets, suggest they look into SeeMS.
Failing all that, issue an error like "this file does not appear to be a Skyline document."