Odd error message in Automation Studio while creating OmniTouchPro design

compuryan

Member
I'm getting the following error on trying to save my new OmniTouchPro design that I have just created and started to work on. This message only came up after I created a button panel for the main menu on the Home page. Any ideas?

Code:
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 AutomationStudio.x01e162e8ea95fafc.WriteMainMenu(clsTSD TS)
   at AutomationStudio.x01e162e8ea95fafc.WriteThemeFile(clsTSD TS)
   at AutomationStudio.x3588e0bc5e1a77f3.SaveThemeFile(String PN, Boolean Check)
   at AutomationStudio.x3588e0bc5e1a77f3.SaveFile(Boolean CheckForChanges)
   at AutomationStudio.x3588e0bc5e1a77f3.SaveFile()
   at AutomationStudio.x10e383b74d703381.SaveProject()
   at AutomationStudio.x210ff09a2516b1a7.SaveProject()
   at AutomationStudio.x210ff09a2516b1a7.tbtnSave_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.3053 (netfxsp.050727-3000)
	CodeBase: file:///c:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
Automation Studio
	Assembly Version: 1.0.3.6
	Win32 Version: 1.0.3.6
	CodeBase: file:///C:/Program%20Files/HAI/Automation%20Studio/Automation%20Studio.exe
----------------------------------------
System.Windows.Forms
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	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.3053 (netfxsp.050727-3000)
	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.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
	Assembly Version: 8.0.0.0
	Win32 Version: 8.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System.Runtime.Remoting
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Configuration
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
OmniTouchPro.Driver.Interfaces
	Assembly Version: 1.0.4309.18950
	Win32 Version: 1.0.4309.18950
	CodeBase: file:///C:/Program%20Files/HAI/Automation%20Studio/OmniTouchPro.Driver.Interfaces.DLL
----------------------------------------
System.Drawing.Design
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
----------------------------------------
Accessibility
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Design
	Assembly Version: 2.0.0.0
	Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000)
	CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.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.
 
and to add to the above, the crashing only starts when I set the "IsMainMenu" property of the button panel to True.
 
Did you start with a blank presentation or are you modifying the default layout?

There are a LOT of parameters that need to be configured so it's recommended to modify the default rather than start with a blank layout.
 
It didn't seem that I was given the option for a default layout for a Pro design. 5.7e, 10p, and 10pe all have default layouts but when I selected Pro it only offered me blank. I tried to do the next best thing which was to import the pages from a 10p panel into the Pro design but that's obviously not going to be flawless. I did look through the design parameters and filled in the blanks where it looked like I needed to, but no luck beyond that.
 
Interesting.
Can you use a 10p or 10pe design and then modify the screen size to fit your project?

A lot of the settings are not in the pages but in the base layout properties tab.
All of the default artwork is stored there.
You may have to fill in every parameter, even if you aren't using them.
It may expect to have a file for each item.

.NullReferenceException: Object reference not set to an instance of an object.

Also I assume you updated to the latest version of Automation Studio.
The version from about 8 months ago was really buggy.
My projects constantly crashed if I moved a single element one pixel.
 
Alright I'll try that... I couldn't find a way to change the screen size before but maybe I was missing something? I do have the latest version though.
 
I'm pretty familiar with AS, but have only used it with the HAI touchscreens.
I was uner the impression the Pro was a module that ran on the non-HAI touchscreen.
The HAI touchscreens just have a locked down module running.
So most of this should be the same.
Will try to help as much as I can.

Because of the constant crashes, I got in the habit of saving each iteration of a design to a new file, 1..0, 2.0, etc. until I knew it wouldn't crash.
That way I could always go back t a previously known good version.

I assume when you add the button menu, you are populating it with icons and setting all the parameters of those icons.
Correct?
 
Yes I have tried both saving with a few icons with all parameters set or an empty button panel and either way get the same result so far.
 
Back
Top