Error when doing tutorial
I am trying to do the nodebox animation tutorial and I am getting this error when I try to connect nodes. Is there a way to fix it? I have been closing and reclosing and it is permanent. If I make a new file and do the exact samething, sometimes it will work. It was happening with the shape tutorial, but I managed to finish it before it made the error again. It is like the file becomes corrupted or something.
java.lang.NullPointerException
at nodebox.client.NetworkView.paintCurrentConnection(NetworkView.java:354)
at nodebox.client.NetworkView.paintComponent(NetworkView.java:303)
at javax.swing.JComponent.paint(JComponent.java:1056)
at javax.swing.JComponent.paintChildren(JComponent.java:889)
at javax.swing.JComponent.paint(JComponent.java:1065)
at javax.swing.JComponent.paintToOffscreen(JComponent.java:5210)
at javax.swing.RepaintManager$PaintManager.paintDoubleBuffered(RepaintManager.java:1579)
at javax.swing.RepaintManager$PaintManager.paint(RepaintManager.java:1502)
at javax.swing.RepaintManager.paint(RepaintManager.java:1272)
at javax.swing.JComponent._paintImmediately(JComponent.java:5158)
at javax.swing.JComponent.paintImmediately(JComponent.java:4969)
at javax.swing.RepaintManager$4.run(RepaintManager.java:831)
at javax.swing.RepaintManager$4.run(RepaintManager.java:814)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:814)
at javax.swing.RepaintManager.paintDirtyRegions(RepaintManager.java:789)
at javax.swing.RepaintManager.prePaintDirtyRegions(RepaintManager.java:738)
at javax.swing.RepaintManager.access$1200(RepaintManager.java:64)
at javax.swing.RepaintManager$ProcessingRunnable.run(RepaintManager.java:1732)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by john on 02 Oct, 2017 02:10 AM
Hi Jamari,
First of all, you should upgrade to NodeBox 3.49 which just came out and fixes one problem with error dialogs.
However, I tried following the animation tutorial using 3.49 and also got an error (though it was different than yours, an out of bounds error (see screenshot).
Error dialogs in NodeBox can be persistent, but you can usually push through them. Mine occurred when I tried to connect the eclipse node to the bounding port of the delete node.
To fix this, you just have to change the Scope in the Delete node from "points" to "paths". The error dialog may pop up again (I got two at once, one on top of the other), but keep closing them until you make the change.
If you are still having trouble, start again, but this time change the Scope to "paths" on the Delete node before you connect it to anything. The tutorial should be updated to include this from now on.
That was the only error I encountered. If yours occurs in a different place, post again and tell us exactly when it occurred, and post your network as well.
I hope Frederik (the creator of NodeBox) will keep working to make error reporting less intrusive.
John
Support Staff 2 Posted by Frederik De Ble... on 15 Nov, 2017 05:18 PM
I'm thinking of this as a fix: a small error icon in the lower-right hand corner instead of this popup dialog.
The error dialogs are really useful for us as developers of the application, but not really for the user.
https://github.com/nodebox/nodebox/issues/438