The support is experimental and limited to GC data.
File > Import failed on Shimadzu QGD files randomly with error code 0x80030057 after Windows 10 Fall Creator update (version 1709) installed . The error occurred more frequently with 2.7 or 64-bit versions. The fix significantly reduces the occurrence of the problem.
Workaround: Updating Windows 10 to the latest update (version 1803) fixes the problem.
File > Import failed on Thermo Raw files acquired with certain MS/MS modes (e.g. targeted MS/MS) with error code 0x80010105.
Tools > VUV Tool failed with uncaught exception for 2.7r2.2 and later versions.
If a CSV file contains empty headers in double quotes, the software did not parse the headers correctly. The affected functionalities include Template > Import Compound List, Project > Import a Sequence Table, and any place that requires importing a CSV file.
For example, Edit > CLIC Expression > Select Blobs with an expression "0 & !((Peak_II > 2.2) & (Peak_II > 2.6) & (Peak_I > 28.6)" selected all blobs, but the expression should always return false.
Workaround: Apply ! to individual terms, for example, "0 & (!(Peak_II > 2.2) | !(Peak_II > 2.6) | !(Peak_I > 28.6)".
An included graphic object with qCLIC that utilizes chemical formula, such as, ABS(MASSRANK(1)-EXACTMASS("C6H2"))<0.05, filtered out all blobs even if there are some blobs satisfying the qCLIC constraint.
The problem is not exposed by any built-in feature in v2.7 or older versions, but may be exposed by a custom report plugin.
Processing > Register Image > check Re-detect blobs and uncheck Show the evaluation report > OK, then the Blob Detection UI showed Before Count as 0 no matter what.
The bug affected all File Format options when a run was processed with a method. For example, with a v2.7 and Later LCxLC edition, open a project > Run > Process Runs with a Agilent 2D-LC CH file > File Format > check Agilent 2D-LC option > Automated Actions > set Use Method with test.method > OK to process. The resulted chromatogram looked like the one manually imported with File > Import menu instead of File > Import Agilent 2D-LC.
Workaround: Specifying automated actions individually instead of using a method when processing a run with any File Format option.
Open a project > create a sequence table > save and close the project > move/rename the project > open the project > Run > Auto Process with the sequence table. The program reported an uncaught exception.
Open a project > Sequences > Export a CSV sequence table > Import Table > choose the CSV table > change the File Type to All Files > Import > OK. The program reported a failure.
Open a project > Sequences > select a sequence table > Edit > Browse the Data File Path. The file chooser title said "Open Methods...".