tag:support.nodebox.net,2012-11-01:/discussions/general-discussion/14711-the-state-of-nodebox-may-2016NodeBox: Discussion 2016-06-01T15:12:57Ztag:support.nodebox.net,2012-11-01:Comment/398974422016-05-17T15:39:29Z2016-05-17T15:39:29ZThe State of NodeBox - May 2016<div><p>Hello John,</p>
<p>Frederik has been very busy on finishing his PhD, and it is
going very well! The public defense will happen on June 15th.
NodeBox Live is very well too, very live and soon kicking, you will
see more of it...uhm soon ;-)<br>
Thanks for your patience and for your active presence on the forum,
it has been helpful for Frederik too.<br>
Lucas</p></div>lucasnijstag:support.nodebox.net,2012-11-01:Comment/398974422016-05-19T07:10:33Z2016-05-19T07:10:33ZThe State of NodeBox - May 2016<div><p>Hi John,</p>
<ul>
<li>I will release a NodeBox 3 update this week. The problem is the
Windows release, which requires a whole setup that occasionally
gets wiped out (because I use a VM, not a real Windows box).</li>
<li>NodeBox Live is doing <em>very</em> well and I plan to open it
up before June 15. The nodocs site is no longer updated,
though.</li>
</ul>
<p>Overall I think we can we do a much better job at communicating
our status, ideas and progress to the community. It's one of the
things I will commit to once the PhD is finished.</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T09:29:15Z2016-05-31T09:29:15ZThe State of NodeBox - May 2016<div><p>We've just released NodeBox 3.0.45 that includes the most recent
bug-fixes.</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T10:08:47Z2016-05-31T10:08:47ZThe State of NodeBox - May 2016<div><p>This is great news, Frederik.</p>
<p>My bug testing network passed with flying colors. But when I
opened one of my larger networks I got an error; it worked fine
before. The network is very complex so I am still trying to track
down the root cause.</p>
<p>Do you have a list of what improvements you made and what nodes
may have new behaviors under 3.45?</p></div>johntag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T10:19:30Z2016-05-31T10:19:30ZThe State of NodeBox - May 2016<div><p>Yeah, those are in the <a href="https://www.nodebox.net/node/release-notes.html">release
notes</a>.</p>
<p>And of course you can look at the <a href="https://github.com/nodebox/nodebox/commits/master">Git commits</a>
to get a down-to-the-source level view of what has changed.</p>
<p>Could you post the error (maybe in another thread?)</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T10:47:03Z2016-05-31T10:47:03ZThe State of NodeBox - May 2016<div><p>I will post the error in a separate thread as soon as I can
isolate and replicate it.</p>
<p>My network has many hundreds of nodes, possibly over a hundred
subnetworks, going up to seven levels deep. The error was a
division by zero error in a "Divide1" node. I have scores of such
nodes with identical names. I eventually found the culprit, buried
six levels deep. Nothing wrong at that level. But the data coming
into that subnetwork under 3.45 is different than the data coming
in under 3.44. So now I have to work my way back up, comparing all
the lists coming in and out of each node under both versions, till
I can find the root cause.</p>
<p>Aside: if you are thinking I am crazy for making such a complex
network, you may be right. But it's a beautiful hi-res dashboard
display (showing changes in an org chart over time and other
related information) that has worked reliably for months now.
Situations like this, however, do expose some of the limitations of
a visual programming language. I've been meaning to start a thread
on that topic.</p>
<p>It's nearly 4 AM here and I have to go to work in the morning,
so I may not be able to get back to you for another day. But I'll
report in as soon as I can isolate the issue.</p>
<p>I am very excited to finally have the nasty intermittent bug
swatted, so thanks again for releasing this new version. I'm sure
we'll get this new wrinkle straightened out soon.</p></div>johntag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T11:35:33Z2016-05-31T11:35:33ZThe State of NodeBox - May 2016<div><p>UPDATE</p>
<p>OK, I didn't go straight to bed. Instead I poked around in some
other networks and soon found what I suspect is the problem.</p>
<p>The problem in another one of my networks was the substring
node. In v44 the index begins with 1. in v45 the index begins with
0. I use the substring node in one of my common subnetworks, which
in turn affects strings used as IDs in filtering many other lists.
As a result, chaos reigns and many errors occur, but they only
appear far downstream of the substring node.</p>
<p>I remember you asked me specifically about making this change,
and I gallantly replied that I would bear the consequences in the
name of zero-index purity. Tomorrow I will verify that the problem
above is due to this change. If it not, and there is some other
issue, I will start a new error thread. Otherwise, I think this is
a feature, not a bug.</p>
<p>I urge you to clarify your release notes, however. Currently all
you say is "improve the string nodes". Pretty vague. It would be a
big help if you would say something like "the substring node index
now begins at 0 instead of 1 - any networks using this node will
need to be updated." What other string nodes did you improve?</p>
<p>I'm off to bed. Thanks!</p>
<p>John</p></div>johntag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T13:20:06Z2016-05-31T13:20:06ZThe State of NodeBox - May 2016<div><p>It would make sense if it is related to the substring node,
since that's been changed.</p>
<p>We'll make the update nodes a bit more clear, especially with
potentially breaking changes.</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T14:17:06Z2016-05-31T14:41:07ZThe State of NodeBox - May 2016<div><p>thanks a lot for taking the time to make the update</p>
<p>problem is it does not seem to run here -Win7 64-<br>
it fails to find jvm.dll, then to locate JNI_CreateJavaVM and to
launch JVM</p>
<p>EDIT: uninstalled and deleted folder, reinstalled and it works
fine now</p></div>riochtag:support.nodebox.net,2012-11-01:Comment/398974422016-05-31T22:53:49Z2016-05-31T22:53:49ZThe State of NodeBox - May 2016<div><p>Hi Frederik,</p>
<p>Just confirming: the change to substring was indeed the cause of
the errors I was experiencing. It turned out that I had 15
occurrences of substring buried at different places in my network.
Fortunately, I was able to fix <em>all</em> of them with one click
by opening the network in a text editor and doing a global search
and replace.</p>
<p>I did encounter one other problem (not an error, but an
appearance change). This one was related to the change you made in
the stack node. It was easily fixed.</p>
<p>While fixing the substring problem I did a quick survey of my
giant network. Here are the stats I came up with:</p>
<p>Total Nodes: 1647<br>
Total Links: 2145<br>
Total Subnetworks: 129<br>
Total Lines in Text file: 6513<br>
Maximum Depth: 7 levels (including main)</p>
<p>Do I win the prize for biggest network?</p>
<p>John</p></div>johntag:support.nodebox.net,2012-11-01:Comment/398974422016-06-01T09:31:10Z2016-06-01T09:31:10ZThe State of NodeBox - May 2016<div><p>@john that is a <em>huge</em> network — I think you
win!</p>
<p>@rioch that's weird. Did you install it over an older version of
NodeBox?</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-06-01T13:37:54Z2016-06-01T13:37:54ZThe State of NodeBox - May 2016<div><p>yes, installed it over previous version, but that was never a
problem before... the same happened on a Win8 system, uninstalling
first seems to do the trick<br>
btw I use the text editor like john says to move nodes between
files: is there any other way, could it be possible to share
clipboard between instances of the software..?</p></div>riochtag:support.nodebox.net,2012-11-01:Comment/398974422016-06-01T15:01:38Z2016-06-01T15:01:38ZThe State of NodeBox - May 2016<div><p>@rioch for the clipboards, if you use File > Open (instead of
double-clicking a file) NodeBox would normally create two documents
in one app instead of two apps with each one document, and you
should be able to copy/paste between those.</p>
<p>This is a distinction between Windows / Mac that we haven't
resolved yet. We could probably add something to the global
clipboard in Windows in a text-only or JSON format...</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/398974422016-06-01T15:12:55Z2016-06-01T15:12:55ZThe State of NodeBox - May 2016<div><p>thanks for the tip, very useful</p>
<p>about the errors, simply uninstalling seemed to work in other
system<br>
it even run fine on a third one but kept both versions installed
-were different paths-<br>
got no more details as it was just a quick test</p></div>rioch