Lang Editor Tool (V1.1 - Spell Checker Added)

[Your Computer]

I cannot re-produce the crash you speak of on my machine running windows 7 x64. If it happens on Linux I cannot make any guarantees about compatibility as this was programmed using c# and the .net framework (along with a call to user32's sendmessage), and it is possible that the freeze is due to the label-edit stuff in the tree view property and it's behaviour on non-windows platforms? It is possible I am not performing the correct sequence of actions however, or that this bug is to do with the loaded file?

Funny thing, i tried to make the program crash again doing the same process, and it didn't crash. However, after several attempts i got it to crash again. Here's the debug info:

Code: (Select All)

System.ArgumentOutOfRangeException: Value has to be >= 0.
Parameter name: length
  at System.Array.Copy (System.Array sourceArray, Int32 sourceIndex, System.Array destinationArray, Int32 destinationIndex, Int32 length) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.TreeNodeCollection.Insert (Int32 index, System.Windows.Forms.TreeNode node) [0x00000] in <filename unknown>:0
  at LangEditor.DisplayForm.addCategory (System.String defaultName) [0x00000] in <filename unknown>:0
  at LangEditor.DisplayForm.addCategoryToolStripMenuItem_Click (System.Object sender, System.EventArgs e) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripItem.OnClick (System.EventArgs e) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripMenuItem.OnClick (System.EventArgs e) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripMenuItem.HandleClick (Int32 mouse_clicks, System.EventArgs e) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripItem.FireEvent (System.EventArgs e, ToolStripItemEventType met) [0x00000] in <filename unknown>:0
  at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem:FireEvent (System.EventArgs,System.Windows.Forms.ToolStripItemEventType)
  at System.Windows.Forms.ToolStrip.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripDropDown.OnMouseUp (System.Windows.Forms.MouseEventArgs mea) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.Control.WmLButtonUp (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.Control.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ScrollableControl.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStrip.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.ToolStripDropDown.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.Control+ControlWindowTarget.OnMessage (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.Control+ControlNativeWindow.WndProc (System.Windows.Forms.Message& m) [0x00000] in <filename unknown>:0
  at System.Windows.Forms.NativeWindow.WndProc (IntPtr hWnd, Msg msg, IntPtr wParam, IntPtr lParam) [0x00000] in <filename unknown>:0

Either this is fixable or it's just purely random. If purely random, then the blame can easily be placed on the mono framework.