Mike Burke 1145825 Posted August 19, 2014 at 09:43 PM Posted August 19, 2014 at 09:43 PM Not sure if there's an approved channel for bug reports - I thought I had seen a github or something earlier but can't track down the URL. If so, direct me there and I can open one up. Entering something goofy like text in ATIS Frequency box causes a crash (blame my inner QA tester). Link to comment Share on other sites More sharing options...
Justin Shannon Posted August 19, 2014 at 09:47 PM Posted August 19, 2014 at 09:47 PM I could have sworn I added a validation check for that...I'll have that fixed in the next update. Thanks for the report. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Ray Lang Posted August 21, 2014 at 09:43 AM Posted August 21, 2014 at 09:43 AM Justin i get the same problem where i get a crash in the atis field. Using the latest update of vAtis. For Wellington Airport (NZWN) the atis freq 126.900 vAtis reports sometimes a invalid freq. ==============================================================================vATIS, Version=1.0.7152.33043, Culture=neutral, PublicKeyToken=null------------------------------------------------------------------------------Application Information------------------------------------------------------------------------------Program : C:\Users\Ray\AppData\Roaming\vATIS\vATIS.exeTime : 21/08/2014 16:54:01OS : Microsoft Windows NT 6.1.7601 Service Pack 1Culture : en-NZProcessors : 4Working Set : 46972928Framework : 2.0.50727.5483Run Time : 00:00:30.3873587------------------------------------------------------------------------------Exception Information------------------------------------------------------------------------------Source : System.Windows.FormsMethod : ShowDialogType : System.InvalidOperationExceptionError : Form that is already visible cannot be displayed as a modal dialog box. Set the form's visible property to false before calling showDialog.Stack Trace : at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) at System.Windows.Forms.Form.ShowDialog() at (Object ) at A.VSB.A(Object A) at A.QF.C(Boolean A, Boolean B) at A.QF.Q(Object A, EventArgs B) at System.Windows.Forms.Control.OnLostFocus(EventArgs e) at System.Windows.Forms.Control.WmKillFocus(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.TextBoxBase.WndProc(Message& m) at System.Windows.Forms.TextBox.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)------------------------------------------------------------------------------2014-08-21_16.54.01.txt============================================================================== Ray Lang Vatsim Senior Supervisor Pacific Oceanic Partnership Admin Have a question? Email [email protected] Link to comment Share on other sites More sharing options...
Justin Shannon Posted August 21, 2014 at 05:25 PM Posted August 21, 2014 at 05:25 PM Ray, I wasn't able to reproduce your error; however, I did make a small change to the validation code, so that may fix the issue. Once I can track down the other crash bug, I'll post an update release. Controller (C3), Los Angeles ARTCC Developer: xPilot, vATIS Link to comment Share on other sites More sharing options...
Recommended Posts