Moving Splitter Throws Exception

  • Thread starter Thread starter sling blade
  • Start date Start date
S

sling blade

I have a form with a one panel docked to the left and a splitter
control docked to the panel. I have no code, events or any other
controls on the form.

When I adjust the splitter (drag it to the right) I get an "External
component has thrown an exception" error when I let go of the mouse
button.

Here is the stack trace.
at
System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMethod
s+IMsoComponetManger.FPush MessageLoop(Int32 dwComponentID, Int32
reason, Int32 pvtLoopData)
at
System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason,
ApplicationContext context)
at
System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run()

If I create a new project and create a form with the panel and splitter
I don't seem to be able to recreate this error.

Should I reload any dll's? Any ideas on what would cause this?
 
sling said:
I have a form with a one panel docked to the left and a splitter
control docked to the panel. I have no code, events or any other
controls on the form.

When I adjust the splitter (drag it to the right) I get an "External
component has thrown an exception" error when I let go of the mouse
button.

Here is the stack trace.
at
System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMethod
s+IMsoComponetManger.FPush MessageLoop(Int32 dwComponentID, Int32
reason, Int32 pvtLoopData)
at
System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason,
ApplicationContext context)
at
System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run()

If I create a new project and create a form with the panel and splitter
I don't seem to be able to recreate this error.

Should I reload any dll's? Any ideas on what would cause this?
Click to expand...
Ahhh, the wonderful world of unexplainable microsoft bugs. Isn't it
wonderful?!
Don't make yourself crazy - it isn't worth it. Trash the bad form and
make a new one.
Although, sometimes just compiling the project resolves some issues.
You might want to try that first.

Tom
 
Thanks for the sound advice.

I went ahead and tried again for the third time and now it seems to be
working.

Go figure!

Thanks again.
 
Back
Top