Bug #56782 MouseWheel in model editor crashes workbench
Submitted: 14 Sep 2010 23:23 Modified: 15 Oct 2010 3:09
Reporter: Graham Charles Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2 OS:Windows
Assigned to: CPU Architecture:Any
Tags: mouse

[14 Sep 2010 23:23] Graham Charles 
Description:
Exception = System.ObjectDisposedException
Message = Cannot access a disposed object.
Object name: 'WorkbenchOverviewForm'.
FullText = System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'WorkbenchOverviewForm'.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.RectangleToScreen(Rectangle r)
   at MySQL.GUI.Workbench.WorkbenchOverviewForm.WheelMessageFilter.PreFilterMessage(Message& m)
   at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(ApplicationContext context)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
Use the mouse wheel when a dialog box is open in the Model editor.

Suggested fix:
Make the mouse wheel not crash the app.
[15 Sep 2010 3:09] Valeriy Kravchuk 
What exact version of Workbench, 5.2.x, do you use?
[15 Oct 2010 23: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".