tag:support.nodebox.net,2012-11-01:/discussions/nodebox-2-3/5999-vexing-behavior-with-latest-nodebox-3050NodeBox: Discussion 2018-04-07T03:56:35Ztag:support.nodebox.net,2012-11-01:Comment/443849312017-12-27T07:41:38Z2017-12-27T07:43:22ZVexing behavior with latest NodeBox 3.0.50<div><p>Frederik,</p>
<p>I like the node connection improvements you introduced with 3.0.50 - MUCH easier to connect nodes now. But I have discovered one unfortunate side-effect.</p>
<p>It is now <em>extremely</em> easy to accidentally tie the output of a node back into one of its input ports. This used to happen rarely, but now happens to me all the time. If you start to make a connection then change your mind and let up on the mouse with the cursor still over the node it will often tie the output back.</p>
<p>It's a very frustrating interaction for beginners. I recently tried showing NodeBox to my daughter and this happened to her pretty much every time she tried to connect two nodes. She was so frustrated that she vowed never to touch NodeBox again!</p>
<p>The problem is doubly disastrous because it not only creates an illegal operation, it also displaces whatever input connection was already there. And the connection is almost invisible, especially if its a black link wrapping back across a black node. The first few times this happened to me I was baffled as to what was going on. Sometimes I don't notice it as first and have to hunt for the invisible link and figure out what previous connection was displaced in order to debug my suddenly buggy network.</p>
<p>After the 400th time this starts to get annoying. But it should be easy to fix.</p>
<p>Since it is <em>always</em> illegal to tie the output of a node back to itself, any attempt to do so should simply be ignored. If you could change the NodeBox interaction so that it is no longer possible to tie an output back to a nodes own input, this frustrating problem would go away forever.</p>
<p>Thanks!</p>
<p>John</p></div>johntag:support.nodebox.net,2012-11-01:Comment/443849312017-12-27T11:18:51Z2017-12-27T11:18:51ZVexing behavior with latest NodeBox 3.0.50<div><p>You're right, that should never happen. I'll implement a fix.</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/443849312018-01-10T09:57:47Z2018-01-10T09:57:47ZVexing behavior with latest NodeBox 3.0.50<div><p>Just downloaded 3.0.51. Works great!</p>
<p>Thanks!</p>
<p>John</p></div>johntag:support.nodebox.net,2012-11-01:Comment/443849312018-01-10T13:15:02Z2018-01-10T13:15:02ZVexing behavior with latest NodeBox 3.0.50<div><p>You're very welcome. Thanks for reporting it!</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/443849312018-04-06T09:32:56Z2018-04-06T09:32:57ZVexing behavior with latest NodeBox 3.0.50<div><p>BoxNode version 3.0.51 (260.6 mb - Mac) dont open on Sierra 10.12.6</p></div>Allantag:support.nodebox.net,2012-11-01:Comment/443849312018-04-07T03:56:34Z2018-04-07T03:56:34ZVexing behavior with latest NodeBox 3.0.50<div><p>Works fine for me on Sierra 10.13.2.</p>
<p>Maybe try upgrading Sierra and see if that helps. If not, we'd need more information to even attempt a diagnosis. Do you get any error messages?</p>
<p>John</p></div>john