Skip to main content
Participant
June 30, 2020
Answered

Disable double click for conversion to path

  • June 30, 2020
  • 4 replies
  • 2598 views

I very often accidentally convert to path the shapes (i.e: rectangles) in my designs, when I just want to dig through the child objects.

I really would like to have the option to disable convert to path with double click. Converting to path should not be that accessible. Once you accidentally convert to path, few saves later, it cannot be switched back... "Convert to Path" should be in the contextual menu or selected element properties menu (right side pane) or through a keyboard shortcut (which already exists).

 

Note: you can revert the convert to path using Esc key only if you just did the conversion, provided that you notice that you notice its icon in the layers view changed to a path icon... Just dont wait too long to revert... you might not be able to do that later.

This topic has been closed for replies.
Correct answer Spas K.

They won't change it because of your feedback, as I've seen relatively few people complain about it.

I agree it's not the best interaction though. It's not about how long you wait, but if you made ANY modifications while in "path mode", even color / shadow, it stays a path.

 

My advice would be to use Ctrl/Cmd+Click instead to select objects that are deep in the groups / layers. This way you can't click too many times, and you can't convert to path while selecting.

4 replies

Participant
March 12, 2024

Please add a way to at least convert the path back to a shape.

jörgw17028522
Participant
November 25, 2021

Oh god, please please add this. Like...tomorrow would be great.

yoozer
Participating Frequently
August 30, 2021

I do agree. This is a pretty bad idea, as a lot of designers are converting shapes by accident. And then we have to redo evrything. Especially because "selecting" stuff is one of the main weaknesses with all Adobe Software for the last decade now.

Not sure why Adobes UX Team was implementing this feature in the first place. Any Head of Design should have a strong enough vision to see this will cause massive problems.

Spas K.
Community Expert
Spas K.Community ExpertCorrect answer
Community Expert
June 30, 2020

They won't change it because of your feedback, as I've seen relatively few people complain about it.

I agree it's not the best interaction though. It's not about how long you wait, but if you made ANY modifications while in "path mode", even color / shadow, it stays a path.

 

My advice would be to use Ctrl/Cmd+Click instead to select objects that are deep in the groups / layers. This way you can't click too many times, and you can't convert to path while selecting.

elNiassAuthor
Participant
July 2, 2020

That's an interesting shortcut you shared, however sometimes you go too deep into the layers and you then have to use the left side layers pane to select the parent layer. It is too many steps in my opinion.

 

Also I have seen around the web, people asking how to convert back things from path to their original non-path type because they had accidentally converted the objects to path. They missed posting it to the adobe community instead.

Spas K.
Community Expert
Community Expert
July 2, 2020

Yeah, there are a lot of bad things about Xd's user experience (ironically). Sometimes you want to click twice and edit it, sometimes you don't. One's faster at the cost of the other.

 

The path thing works the same way as Illustrator and Photoshop, once it's a path, unless you can undo with Ctrl/Cmd+Z, it's done.

 

That's logical, since primitives and paths are treated differently, as you can edit some traits of a primitive - imagine a polygon, you can add corners, round them and do all sorts of things. If you move or add a point, then the relationship between the points becomes "custom" and no longer fits the algorithm.

 

With that said, the software should be able to tell the difference between a moved point and a color changed. And if you haven't moved any points, it should stay a primitive. I guess that's too much to ask provided we don't even have dark mode yet 🙂