NakedMarkets Forum

I simply typed in a large lot size and didnt even submit accept in the pending order box and it completely crashed the program. Here is the error log:



#####-- 13/11/2022 12:43:24 --#####
System.ArgumentOutOfRangeException: Value of '200.38' is not valid for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
Parameter name: Value
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at ’‹.‹ž(Object , Decimal , ’‹ )
at NakedMarkets.Forms.PendingOrderForm.‡š˜(Object , EventArgs )
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.UpDownBase.OnTextBoxTextChanged(Object source, EventArgs e)
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
at System.Windows.Forms.Control.set_Text(String value)
at System.Windows.Forms.TextBoxBase.set_Text(String value)
at System.Windows.Forms.UpDownBase.UpDownEdit.set_Text(String value)
at System.Windows.Forms.UpDownBase.set_Text(String value)
at System.Windows.Forms.NumericUpDown.set_Text(String value)
at System.Windows.Forms.NumericUpDown.UpdateEditText()
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at ’‹.‹ž(Object , Decimal , ’‹ )
at NakedMarkets.Forms.PendingOrderForm.‡š™(Object , EventArgs )
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.UpDownBase.OnTextBoxTextChanged(Object source, EventArgs e)
at System.Windows.Forms.Control.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.OnTextChanged(EventArgs e)
at System.Windows.Forms.TextBoxBase.WmReflectCommand(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)

Thanks, it will be fixed in the next release this week.

Thanks for your report, it has been fixed in the latest release