Bug #67438 Upgrade to Windows 8 then SplitterDistance error
Submitted: 31 Oct 2012 12:56 Modified: 30 Nov 2012 13:58
Reporter: Matt Burgess Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.2.36 CE OS:Windows (8)
Assigned to: CPU Architecture:Any

[31 Oct 2012 12:56] Matt Burgess 
Description:
I upgraded my laptop to Windows 8.  Now when I try to connect to the databases that previously worked in Windows 7 I get the following error: Value of '-2' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.

The backtrace is below from the log file.

08:49:51 [   Info][      Workbench]: Setting up main UI
08:49:51 [   Info][      Workbench]: UI is up
08:49:51 [   Info][      Workbench]: Running the application
08:50:02 [   Info][     SSH tunnel]: Starting tunnel
08:50:04 [   Info][        WQE.net]: Launching SQL IDE
08:50:04 [  Error][      Workbench]: Value of '-2' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
Exception = System.ArgumentOutOfRangeException
Message = Value of '-2' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
FullText = System.ArgumentOutOfRangeException: Value of '-2' 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:
Open MySql Workbench in Windows 8 and double-click a database connection.
[31 Oct 2012 13:58] MySQL Verification Team 
Please try version 5.2.44. Thanks.
[1 Dec 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".