UPDATE: The poll is closed, but scroll down for a new beta release.
We’re about to start on the changes to node editing, specifically allowing keyboard nudges for nodes based on the “what do you want changed” thread from a month ago. We were starting here because it seemed like a simple change to knock out. Of course, it’s one of the oldest parts of the code, so it’s more invasive than we expected. Since we’re here anyway, we’d like your opinion on a larger change that we might make.
Currently, node editing is tied to the current selection. If you click away, it closes the command.
Would you prefer making node editing more of a modal or persistent command that lets you change the selection, but the command must be explicitly ended with a button press or escape key.
Leave the command as-is, with the command ending when you click away from the vectors
Change to a persistent command or a mode that allows changing selection
0voters
Please vote, but feel free to add justification for your selection below based on other CAD or design software.
This could end up being a huge internal change, so it might get deferred behind other features, but we’d like to figure out if it’s even a desirable change.
I would like to see it go modal — AND be consistent with all your other dialogs. One of the feature requests is this one, that I put in a while ago. It would be great if things behaved consistently in different parts of the product. [EDIT] I just checked, and Node Edit dialog was in that original request…to go modal!
If I was on my phone, I could post a photo of your document sitting on my desk right now.
Part of the original design for CC was for the commands to be contextual, where only valid commands (based on selection or other state) are shown. Changing to modal commands begins to break this apart. But CC has grown way beyond anything we originally expected, so it’s fine to change it if it needs to be changed.
(EDIT- to put a finer point on it, if we make this change, CC will become less consistent before it becomes more consistent. That’s OK for me- I care more about usability than consistency for its own sake.)
I voted for the persistent command but now that I think about my particular work flow, I see where that wouldn’t make much of a difference to me. Currently, if I need to node edit several vectors, whether they are closed or open vectors, I just select all then enter the node edit mode. After editing what I needed on any of the vectors selected I click done. Really no switching back and forth. Maybe I’m missing something here in the intent of a persistent command.
I do notice accidentally clicking open space & dismissing the dialog, then needing to reopen it.
Object selection is sometimes fussy, and you need to watch the cursor to know what you’re selecting.
While it’s an extra motion/click to “Cancel” or “Done” the dialog, if you’re editing a lot of nodes it will be more efficient. If only editing one or two, it would be quicker, or a wash the current way.
I think the most frustrating part is not snapping to other nodes when moving a node. It will snap to a grid, which may or may not be desirable. You have to Zoom way in to place a node near a grid but not directly on it.
It’s safe to say that the opinion is an overwhelming “Yes, let’s do modal,” so we’ll give it a shot.
I think our take on it will probably include:
An option to lock the current selection so an errant click doesn’t deselect anything. I think that would probably be a win for the users who like the current system.
Possibly a separate toggle for snapping in node editing, since this is a different mode than the global state, where you drag complete vectors.
We just posted 817 to beta with the new node editing command. Top-line changes include:
Node editing is now modal
Snapping can be toggled with F4
When node editing, you can disable snapping by holding Alt/Option when dragging
While node editing and hovering on a curve, you can press I to insert a node, or C to cut the vector at that point.
You can nudge selected nodes with the cursor keys
And of course, our code signing token disconnected itself from our remote build machine, so this beta is not signed on Windows.
This is really a work-in-progress release since there are things (like popup menus on right-click) that are not implemented yet. But, this is a massive change of some of the oldest, crustiest parts of CC, so we wanted to get eyes on it sooner rather than later. As it is right now, I think it’s a solid improvement.
