I just want to select the right one to delete instead ot deleting the wrong one then ctrl+z then selecting the other one and deleting again. If there is a way to know which node belongs to which segment please let me know :). Thanks in advance! :)
Wonder how 3 month old threads are turning up at the top of the forum lists. But anyways the answer is the TAB key.
Hitting TAB or Shift+Tab will cycle thru the nodes from the selected node, forward or backward respectively. Experiment and you will find the best way to use this tip to select and move / delete the node you want thats best suited to your workflow.
For example lets assume you have broken a node between two other nodes. Select the next node on the path based on the direction and hit ***+Tab to get tot the start node of that segment or select the previous node and hit TAB to get to the end node of the previous segment.
Another example, when you break a node, one node of the node that was just broken into two, will remain selected. The selected node will always be the start node of the next segment of the path based on the path direction. Delete the node or use Tab or Shift+TAB as desired.
Someday maybe I should sit down and compile a list of such hidden shortcuts I've discovered down the line and just assumed that everyone knew them anyways!
Nice Suku, a question if you are Tabbing through nodes and you delete a node you don't need is there a way of deleting and keeping the selection on the next node in the sequence? ATM if you delete the node you have to use the cursor to reselect the next node.
Sorry Chris, as of v2017, I don't think what you ask is possible.
I wrote a VBA macro with a couple of subroutines:
For the video linked to below, in the Curve Editing shortcut key table, I have "X" assigned to the "next" sub, and "Z" assigned to the "previous" sub.
VIDEO: delete node, select next or previous
Here's a .ZIP archive with the .GMS file:
I don't have much experience manipulating curves/subpaths/nodes using the API, but for my simple tests so far, the macro appears to be working as intended.
Hey thanks John, this would be handy for cleaning up crappy vectors you get from time to time.