Snap to Nodes

[David Baay]

As pointed out, all you need to do is delete the redundant node and (if necessary) change the segment type to something other than Jump. This is not a workaround; this it how it's intended to be used. Creating a new type of snap object to facilitate stacking redundant nodes is not a feature anyone should support.

[murat k.]

1 hour ago, David Baay said:

As pointed out, all you need to do is delete the redundant node and (if necessary) change the segment type to something other than Jump. This is not a workaround; this it how it's intended to be used. Creating a new type of snap object to facilitate stacking redundant nodes is not a feature anyone should support.

Please stop accepting workarounds as solutions and support someone when they come up with a real solution, or stay silent. Otherwise, you're not helping either the development of Cakewalk or those trying to support its progress.

[David Baay]

What part of "This is not a workaround" didn't you understand? A workaround is a way of overcoming a bonafide software defect or a significant omission in functionality. Moreover a workaround is typically awkward, requires more steps to accomplish and/or yields a result that is not completely satisfactory. None of that is the case here. In fact your "solution" is arguably more awkward, requiring that you enable/disable snap or use modifiers, depending on the situation, that you drag and drop the node with sufficient precision to ensure that it snaps to the correct target, and potentially has an unsatisfactory result (duplicate nodes) unless programmers add logic to eliminate it... oh, wait, that would be just like deleting it in the first place!

P.S. If you want to have a discussion about which of us has contributed more to the development and success of Cakewalk and its user community, come back in 30 years and we'll compare notes.

Edited October 25 by David Baay

[murat k.]

The significant functional gap is ensuring that two nodes become a single node when we bring them closer together. When we delete a node, there are two possibilities: it will either connect to the other node or it won’t. Sometimes it connects, and sometimes it doesn’t. So, there is no solution in place.

When a node is brought close to another node and it’s not intended to snap, snapping function can temporarily be disabled or enabled with a modifier, which is something we've been doing for other things as well, so there’s nothing awkward about it.

P.S. I have no intention of competing with anyone; my goal is to contribute to the development of Cakewalk. Your attitude here seems intent on maintaining the status quo, which clearly hinders progress.

[murat k.]

I hadn’t detailed the topic, thinking that the developers would find the most suitable method. However, to clarify a few things, this issue can be solved as follows.

The Ctrl modifier is quite suitable for temporary node snapping. Currently, there are already situations where it partially functions as a snap feature. It's important to remember that the snapped nodes need to merge into a single node. This way, when we drag a node, another node won't unexpectedly appear underneath it.

However, I believe we also need a global on/off toggle to enable or disable node snapping. This would be bind to the global snap function but could be an option that can be toggled, allowing us to continue working with a single shortcut for snapping, just like we do now.