Bug #63763 System.ArgumentOutOfRangeException
Submitted: 15 Dec 2011 18:49 Modified: 25 Dec 2019 11:13
Reporter: Girish Showkatramani Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[15 Dec 2011 18:49] Girish Showkatramani 
Description:
Exception = System.ArgumentOutOfRangeException
Message = Value of '-1' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
FullText = System.ArgumentOutOfRangeException: Value of '-1' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
   at System.Windows.Forms.SplitContainer.set_SplitterDistance(Int32 value)
   at MySQL.GUI.Workbench.DbSqlEditor.AddSqlEditor(Int32 index)
   at MySQL.GUI.Workbench.DbSqlEditor.Initialize()
   at MySQL.GUI.Workbench.DbSqlEditor..ctor(WbContext wbContext, UIForm uiForm)
   at MySQL.GUI.Workbench.MainForm.CreateMainFormView(String ViewName, UIForm viewBE)

How to repeat:
Exception = System.ArgumentOutOfRangeException
Message = Value of '-1' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
FullText = System.ArgumentOutOfRangeException: Value of '-1' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
   at System.Windows.Forms.SplitContainer.set_SplitterDistance(Int32 value)
   at MySQL.GUI.Workbench.DbSqlEditor.AddSqlEditor(Int32 index)
   at MySQL.GUI.Workbench.DbSqlEditor.Initialize()
   at MySQL.GUI.Workbench.DbSqlEditor..ctor(WbContext wbContext, UIForm uiForm)
   at MySQL.GUI.Workbench.MainForm.CreateMainFormView(String ViewName, UIForm viewBE)
[15 Dec 2011 18:52] Valeriy Kravchuk 
What exact version, 5.2.x, do you use?
[16 Jan 2012 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".