double-click time to short
With a fast double-click I'm initially able to create a new node. Over time, it seems to require a fast and faster double-click to work. If I save my project and restart NodeBox it's better for a while. Also seems to get worse as the project gets more complex.
MacBook Pro running Catalina. With only a few hours experience with NodeBox I'm loving it, but this issue is becoming a show stopper.
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 11 Dec, 2020 11:36 PM
Chaynese56,
Welcome to the NodeBox community.
I am also running NodeBox under Catalina on a MacBook Pro, though I exclusively use the trackpad. If you're using a mouse you might try switching to the trackpad (you can get a separate trackpad if you are using your MacBook with a separate keyboard and monitor) and see if that helps.
Either way, you might try adjusting the click settings to see if that helps. My trackpad point and click settings are Light Click and Fast Tracking Speed. I can't remember how I had my mouse set up when I was using one.
Another thing you could try is control clicking and using the New Node popup menu instead of double clicking. It's two single clicks instead of one double-click, but not much slower and you could probably get used to it.
I have occasionally noticed some issues with double-clicking to place new nodes, but not enough to bother me. I hadn't noticed a degradation over time, but will keep an eye out to see if I can replicate it.
The NodeBox UI has a number of other rough edges. Sometimes, well into a session, it will sometimes stop registering keyboard shortcuts (like command S to save). Rebooting will fix that.
I regularly run into other things that annoy me. When control clicking to drill into a subnetwork I often have the cursor near the output port instead of fully inside the node and get the New Node menu instead. Even after all these years I still sometimes have trouble linking one node to another; I stretch the link to an input port but let up a fraction of a second too soon.
I also have a list of improvements, like the ability to drag a node over an existing link to insert it into a chain instantly, a visual distinction between the two types of link (value vs. list), the ability to set link type when publishing, the ability to rename and reorder ports directly from the metadata dialog, etc. Each is small, but together could greatly improve the overall experience.
I was an interaction designer before my recent retirement, and have long wished to sand off these rough edges. A few minor improvements could make NodeBox less frustrating, more efficient, and much more pleasant to use overall, especially for hardcore users like me. Sadly, I don't expect Frederik will have the time or inclination to do those fixes anytime soon.
That said, I still find NodeBox to be a wonderful tool, ideal for playing, and unlike any other tool out there. Other tools are more powerful, but are also more cluttered and confusing. NodeBox retains a wonderful simplicity, both in its interface and in its overall architecture, that, to me, more than compensates for its shortcomings.
I hope you will stick with NodeBox. After a few weeks of steady use you may develop muscle memory to adapt to a rhythm that reduces the friction. I think you will find that the more you use it, the more you will like it, and the more you will be able to do with it.
Also please share your experiences, suggestions, and (if you're comfortable) examples of your work here on the forum.
Happy Nodeboxing!
John
2 Posted by chaynes56 on 14 Dec, 2020 09:23 PM
Thanks for your detailed reply, John. To create a new node, I still have to double-click on the node type in the new-node list. For some reason it’s working better now. Still sometimes a problem, but can live with it as it is now. Double-clicking with the mouse isn’t a problem with other software. I noticed sometimes it actually worked after a delay of more than a second. It could be by expecting something faster and trying again, I was messing it up.
Your UI suggestions sound great. Hope they happen somehow, someday. I’ve just started a “point confusion or bug” conversation that it seems you’re experience could address well.
Regards,
Chris
3 Posted by chaynes56 on 15 Dec, 2020 08:05 PM
I find now that in the node list, return creates the selected node, so for node creation I can indeed work without double-click, though it mostly works.