Frederik,
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.
It is now extremely 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.
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!
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.
After the 400th time this starts to get annoying. But it should be easy to fix.
Since it is always 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.
Thanks!
John