forum.cncdrive.com

I'm working on a new screenset, and ran into a problem.
I started with the default screenset, and deleted all of the elements from the Run screen.
When I tried to add a Toolpath Window, it would add it to the upper left corner, and when I clicked on it, it would cause an exception. I could not select it or do anything with it. (I'll post the exception error in a separate post)
I then opened the .ssf file, and saw that it was on layer 1.
Changing it to layer 2, and restarting UCCNC, it was now in the center of the screen, and I could now edit it normally.

If you Edit Screen, and change a toolpath window layer to layer 1, then select it , it will cause a crash.

I don't know why my elements are being created on layer 1? Would it be possible to specify the layer when adding items to the screen?

Here's the Exception Error:

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 UCCNC.GUI.Gettoolpathviewproperties(Int32 )
at UCCNC.GUI.toolpathview_mousedown(Object , MouseEventArgs )
at UCCNC.Form1.glControl1_MouseDown(Object , MouseEventArgs )
at System.Windows.Forms.Control.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.UserControl.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(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.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.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.8745 (WinRel.050727-8700)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
UCCNC
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/UCCNC.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
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.8745 (WinRel.050727-8700)
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.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
OpenTK
Assembly Version: 1.1.0.0
Win32 Version: 1.1.1664.6217
CodeBase: file:///D:/UCCNC/OpenTK.DLL
----------------------------------------
뢷绛왃嬂Ýү됥ብ
Assembly Version: 0.0.65535.65535
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/UCCNC.exe
----------------------------------------
OpenTK.GLControl
Assembly Version: 1.1.0.0
Win32 Version: 1.1.1664.6217
CodeBase: file:///D:/UCCNC/OpenTK.GLControl.DLL
----------------------------------------
OpenTK.Compatibility
Assembly Version: 1.1.0.0
Win32 Version: 1.1.1664.6217
CodeBase: file:///D:/UCCNC/OpenTK.Compatibility.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
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.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
ILCalc
Assembly Version: 0.9.7.5
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/UCCNC.exe
----------------------------------------
6ub3ix9q
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Web
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Web/2.0.0.0__b03f5f7f11d50a3a/System.Web.dll
----------------------------------------
Plugininterface
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugininterface.DLL
----------------------------------------
AutoLevelerCA
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/AutoLevelerCA.dll
----------------------------------------
Debugger
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Debugger.dll
----------------------------------------
Diagnostics
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Diagnostics.dll
----------------------------------------
Laserengrave
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Laserengrave.dll
----------------------------------------
Modbusmaster
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Modbusmaster.dll
----------------------------------------
Plugintest
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Plugintest.dll
----------------------------------------
Printer3D
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Printer3D.dll
----------------------------------------
Scope
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Scope.dll
----------------------------------------
UCR200Plugin
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/UCR200Plugin.dll
----------------------------------------
Webcamera
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Webcamera.dll
----------------------------------------
Xbox360controller
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/Xbox360controller.dll
----------------------------------------
XHC-HB04_pendant
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/UCCNC/Plugins/XHC-HB04_pendant.dll
----------------------------------------
upmcujgv
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
0um2h_yf
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
zxwnxnnh
Assembly Version: 0.0.0.0
Win32 Version: 2.0.50727.8745 (WinRel.050727-8700)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.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.

Yes, but even though I don't have the jog screen open, everything I add is being placed on Layer 1.

Have you tried editing the screenset in notepad++?

I just used regular Notepad to change it to Layer 2 and then it was fine.

But you can get it to crash by clicking on a toolpath window on Layer 1. This should be fixed.

I wasn't sure if it was because you deleted all the objects off a screenset and something was not removed


Hence I thought maybe if you started with a blank ssf? File you'll be guaranteed that there is no potential bad code in it.

No. Just select your toolpath with the screen editor, and change the layer to 1. Then click on it.

Hmm... it may not be a bug...

The problem is that the layer number is also the tab number.... hence with making it layer 1, you are essentially putting it on the main screen, but there are also 2 other screensets on other tab layers (in my ssf file) at least. hence you're trying to show a toolpath on the main layer and on two other child layers.... hence you're asking for the same information to be displayed on the main screen and child layers, and because it is "dynamic" information the software may not like this loop / double hungry resource you've ask it to perform simultaneously....

AS3.Addtoolpath(80, 39, 372, 306, 2);
AS3.Addtoolpath(117, 33, 792, 561, 3);
AS3.Addtoolpath(671, 53, 228, 216, 45);

Maybe it is a bug.... [depends of definition of "bug" .... if I keep touching the live wire and getting a shock, the resolution is sometimes easier to stop touching the live wire than just replace the cable / connector ]

[I've just found other bits missing from the manual but looking through that SSF file, thanks ... like AS3.Addtoolpath and AS3.AddUCCAM]

I should have added, I think the main screen layer 1 is the background screen...I.e the right hand side buttons plus cncdrive logo

I deleted everything from the Run screen except the tab buttons at the top, and changed the background image.
If I click on the background, it tells me it's on layer 2. But if I add anything, it wants to put them on layer 1 by default. Which led to the crash.....