Beta 1.1 - double clicking in text mode should not activate node editing mode
-
@vectoradmin I am noticing the double click to enter node editing mode (that's what I have the standard double-click now set up to do) not only interferes with double clicking live type to select it all, but it also affects when I double click on a node handle to delete it and make that side a cusp edge
You can see in this video as I select different nodes and double their handle to remove them and make the cusp side.... the first one worked fine, the second one did not - it ironically switched the transform tool when in that case I want it to remain in the node editing tool
I don't know what the best solution would be aside from either removing the new node editing feature from the solo double click and keeping the shift and option modifiers for those tasks
or I select a node handle and remove it with the delete key. Ideally there's got to be a way to differentiate between someone is double clicking on a node handle versus clicking on any other part of a vector shape - just like there needs to be a way to not allow a double click to do anything aside from highlighting text when selecting live type as discussed earlier in the thread.
If there's a way to turn off the new double click function for node handles and live text - would that solve the issues and still allow a double click to have an added function?
-
@Ingolf @Boldline @b77 @Ingolf Looks like there are some implications of the new double click handling causing bugs.
These will be fixed.
-
@vectoradmin Even when I have the double click sans modifiers set to none - I still can't double click to select live text.
-
@Boldline Set it for now to ‘Isolate Selected’ (the default) and text editing should work.
-
@b77 Where do I do that? Am I missing it?
-
@Boldline It’s the second in the list.
-
@b77 ok I get it now - I was looking for a literal "default" but right now "isolate selected" would be default - thanks!
-
@Boldline Should the developer add ‘(Default)’ after ‘Isolate Selected’?
-
@b77 No, I don't think so because "default" won't mean anything once he fixes the issues with it with live text and double clicking node handles to remove them. I was not necessarily looking for literal "default" wording initially but was just in the mindset based on your reply.That was just me misunderstanding your answer - nothing you did wrong
-
@Ingolf This issue should be fixed in the new build 1.1.002 (beta)
