unhandled exception

[GoogleCodeExporter]

What steps will reproduce the problem?
After making a "new arduino" I clicked clone (I clicked it because there was no 
graph, the program doesnt seem to work) and it poped out this message:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an 
object.
   at XOscillo.DataBlock..ctor(DataBlock db)
   at XOscillo.GraphControl.GetScopeData()
   at XOscillo.VizArduino.GetDataBlock()
   at XOscillo.VizBuffer.CopyFrom(VizForm vf)
   at XOscillo.VizForm.Clone()
   at XOscillo.VizArduino.clone_Click(Object sender, EventArgs e)
   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   at System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
XOscillo
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Documents%20and%20Settings/stbn/Mis%20documentos/Descargas/XOscillo_20110302v5/XOscillo.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.42 (RTM.050727-4200)
    CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Original issue reported on code.google.com by estepa...@gmail.com on 6 Apr 2011 at 4:35

[GoogleCodeExporter]

it seems that the program throws this exception when I try to open menus once 
created the arduino

Original comment by estepa...@gmail.com on 6 Apr 2011 at 4:43

[GoogleCodeExporter]

I think this error is caused because the graph isnt generated until the first 
voltage read

Original comment by estepa...@gmail.com on 6 Apr 2011 at 10:22

[GoogleCodeExporter]

Well.. Maybe I found the origin of all those exceptions.. Maybe, it is that for 
some reason, the oscilloscope doesnt start until there is a significative read 
in the arduino board, so the window wont work, and neither the controls (today 
I tried to use Xoscillo and it worked, not as yesterday)

Original comment by estepa...@gmail.com on 7 Apr 2011 at 7:34

[GoogleCodeExporter]

Also, your program only works with "well built" circuits, when it triggers the 
"tools" (as decode frequency) will work, otherways it won't

Original comment by estepa...@gmail.com on 7 Apr 2011 at 8:19

[GoogleCodeExporter]

Original comment by aguav...@gmail.com on 8 Feb 2013 at 12:31

• Changed state: Fixed