Hi,

We updated skyline daily yesterday (to Skyline-daily 64-bit 3.6.1.10405 ) and tried to build a (dda) spectral library (using iProphet files). The process fails with the following error. I repeated the process using PD output (msf files) and get the same error. The sample has Biognosys-11 iRT standard peptides (and I checked that I can see them in my search results). Could you please help.

Thanks!
Datta.


===============================================================================================
=============================== E R R O R =====================================================
"An error occurred trying to add iRTs to the library. Cannot access a disposed object. Object name: 'LongWaitDlg'"

================================================================================================
=========================== M O R E I N F O =================================================
System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'LongWaitDlg'.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
   at pwiz.Skyline.Controls.LongWaitDlg.PerformWork(Control parent, Int32 delayMillis, Action`1 performWork) in c:\proj\pwiz_x64\pwiz_tools\Skyline\Controls\LongWaitDlg.cs:line 157
   at pwiz.Skyline.Controls.LongWaitDlg.PerformWork(Control parent, Int32 delayMillis, Action`1 performWork) in c:\proj\pwiz_x64\pwiz_tools\Skyline\Controls\LongWaitDlg.cs:line 130
   at pwiz.Skyline.SettingsUI.LibraryBuildNotificationHandler.AddIrts(BuildState buildState) in c:\proj\pwiz_x64\pwiz_tools\Skyline\SettingsUI\BuildLibraryNotification.cs:line 368

Yeah, I got that two preparing for yesterday's webinar. This is a bug in the new code to add iRT information to the library, new to this latest build. Kaipo is working on it, but for now just avoid specifying your iRT standards when you build libraries. That is backed by new code which apparently has this bug.

Thanks for reporting it!

Pretty sure we fixed this a while ago.