MySQL Bugs: #67940: Error occurred opening a sql editor tab as a db connection was established

Bug #67940	Error occurred opening a sql editor tab as a db connection was established
Submitted:	18 Dec 2012 18:28	Modified:	2 Feb 2013 0:04
Reporter:	Kurt Longnecker	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.45	OS:	Windows (Microsoft (build 9200), 64-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
I opened a connection which resulted in the sql editor opening and producing this error. The object browser and snippets panes are now to the right of the sql editorregion/pane.

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.44  revision 9933
Configuration Directory: C:\Users\Kurt\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft  (build 9200), 64-bit
CPU: 8x Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz, 7.9 GiB RAM
Active video adapter (2): Intel(R) HD Graphics 4000
Installed video RAM: -1984 MB
Current video mode: 1920 x 1080 x 4294967296 colors
Used bit depth: 32
Driver version: 9.17.10.2849
Installed display drivers: igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32
Current user language: English (United States)

Exception = System.ArgumentOutOfRangeException
Message = Value of '-65' is not valid for 'SplitterDistance'. 'SplitterDistance' must be greater than 0.
Parameter name: SplitterDistance
FullText = System.ArgumentOutOfRangeException: Value of '-65' 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.SqlIdeForm.LoadFormState()
   at MySQL.GUI.Workbench.SqlIdeForm.DbSqlEditor_Shown(Object sender, EventArgs e)
   at System.Windows.Forms.Form.OnShown(EventArgs e)
   at System.Windows.Forms.Form.CallShownEvent()
   at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
   at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

How to repeat:
Not sure, but it keeps happening for me when I simply repeat what I have already stated.

I recall what created this situation. On the toolbar in the SQL Editor - top right-hand corner, there are buttons to toggle the visibility of different panes like snippets, object browser, etc. I tried these buttons for the first time within the last week. When a hidden pane is restored, it is not restored in the same position. The object browser is restored to the right of everything else and takes up a considerable portion of the screen. Resizing things doesn't stick, so now every time the editor is opened, the splitter error occurs.

Please try version 5.2.45. Thanks.

This bug still exists in v5.2.45.

Error message dialog

Attachment: error_msg.png (image/png, text), 44.32 KiB.

Thank you for the feedback. Which exactly version of Windows OS are you using?. Thanks.

Hi Miguel, I'm using Windows 8 64-bit. Hope that is helpful. Thanks for investigating this bug.

Hi Miguel, I'm using Windows 8 64-bit. Hope that is helpful. Thanks for investigating this bug.

Thank you for the feedback. I couldn't repeat on Windows 7 and 8. Beside you description about how to repeat have you some idea of some special condition is necessary i.e you have done some edit in preferences?. Thanks.

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".