Photoshop: Vector Shapes & path highlight/selection issue

  • 44
  • Problem
  • Updated 6 years ago
  • Solved
  • (Edited)
Hi there,

Photoshop CS5

1.Vector shape have color area and vector mask visible - http://screencast.com/t/hVB2H7ceqp
2. Selecting the later do not affect the visibility of the actual shape - http://screencast.com/t/YkmJlsLRNX
3. Selecting the vector mask gives us the visual representation that mask is selected - http://screencast.com/t/Iq4P9Qgp9

Photoshop CS6 beta

1. Vector shape have a single icon - http://screencast.com/t/ptBpMRYup
2. When select the layer the vector mask is automatic selected too - http://screencast.com/t/dm1WjibiTZ
This is frustrating because it is hard to set layer styles properly, the additional "stroke" that comes from the selected layer mask visuals mess the things up.

Please can you find a way to select vector shapes without selecting the actual vector mask too, this was perfectly developed in Photoshop CS5.

Thanks!

Regards,
SK
Photo of kckfm

kckfm

  • 35 Posts
  • 2 Reply Likes

Posted 7 years ago

  • 44
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
Adobe, this is a JDI issue here and this needs to be "fixed". Its driving me mad! This is a poor call to have changed this process that worked just fine before. Can we have some response as to what, if anything is going to be done about this? I'm wasting hours for no obvious gain. Why has this changed? I'll be cancelling my CS6 subscription and sticking with CS5 if this doesnt get fixed. Whomever made this call needs to be fired!
Photo of David Homolicsan

David Homolicsan

  • 1 Post
  • 1 Reply Like
Many complaintes, unanswered!
why did we pay for this software if we cant work with it!
Going back to cs5.
Photo of jordan grosz

jordan grosz

  • 23 Posts
  • 0 Reply Likes
Use ctrl+Shft+H or option+shft+H on mac. That will hide all the control points when not using vector editing tools.
It toggles them on and off and unlike using the enter button it will not revert back if you select another tool or layer and then come back.
Photo of a k

a k

  • 6 Posts
  • 1 Reply Like
I like to think that this is adobe right now: http://i.imgur.com/UCL9S.gif
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
This kind of basic functionality change is indefensible. Didn't anybody TEST this?
Photo of Nicholas Terry

Nicholas Terry

  • 5 Posts
  • 1 Reply Like
I'm not sure if you guys have also come across this one, but:

It takes another few clicks to add a shape to a vector mask since selecting a layer and then clicking the mask tool twice creates a vector mask, but doesn't automatically select it and you have to change the shape type manually to path by clicking and then back to shape when you are done (old work flow for vector masks using shapes: select layer, press mask button twice, press u (pull up shape tool), draw on canvas (hold shift) where you want the mask. new work flow: select layer, press mask button twice, select vector mask on layer, press u (pull up shape tool), click on the drop down select menu for shape and pick path, draw on canvas (hold shift) where you want the mask - the new work flow has two more steps that require mouse clicking 3 times in different areas of the interface which over repeated use becomes quite unsavory)...
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
Ring, ring, ring. (rings bell on the desk in the empty foyer lobby of Adobe customer support)
"Hello, is anybody there? Customers waiting for some service please" An update would be appreciated."
Ring, ring, ring.
"... hello ...."
"... anybody ... ?"
Photo of OJ

OJ

  • 19 Posts
  • 1 Reply Like
This is horrendous. Photoshop is almost unusable because of the badge over shapes, and the inability to deselect a layer mask. Fix it immediately. I'm requesting a refund from Adobe until then.
Photo of JEREMY SALLEE

JEREMY SALLEE

  • 11 Posts
  • 1 Reply Like
Is ADOBE even reading this? Can someone from ADOBE come and reply to this thread where so far a HUGE amount of designers have been complaining.

Come on adobe, start listening to your users... Why do we pay such a HUGE amount of money for your softwares if even your customer support is evidently lacking of efficiency AND communication...
Photo of JEREMY SALLEE

JEREMY SALLEE

  • 11 Posts
  • 1 Reply Like
This feedback website seems to be useless.
Nobody from adobe is communicating. Is there someone around here even reading this thread?
Photo of Nicholas Terry

Nicholas Terry

  • 5 Posts
  • 1 Reply Like
Maybe tweet @jtranber - he seems active..
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
Just tweeted @Adobe and @Photoshop. Make noise until someone listens. Pretty appalling support IMVHO and so making this a PR nightmare is step 1.
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
might aswell tweet to @ImNotListeningToMyCustomers aswell
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
Why are you trying to make noise? This issue is already acknowledged, and already discussed in a dozen other places.
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
Hmm, let me respond to that Chris on behalf of all of us who have "wasted our time" with highlighting this irritating "issue" and to your thoughtful response.

This is how that response makes me feel: Patronised, annoyed, ignored, unheard - these are the sanitised responses - I could add a whole lot more that wouldnt get through the filter.

Very disappointed at such a response. When Adobe make you jobless you for comments like that, please dont work in a hospital Chris in patient care, otherwise you might end up saying to someone who's just been rushed in from a car crash "Why are you crying and screaming in pain? We can see you're not doing well, we've seen it all before though. Goodbye."

Nice one Chris! Way to go.
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
Why are you trying to make noise?
Because being quiet accomplishes nothing.

This issue is already acknowledged
WHERE?? How about a LINK.

and already discussed in a dozen other places
DITTO

Usefulness of answer: 0
Photo of a k

a k

  • 6 Posts
  • 1 Reply Like
We know you're aware of this issue. But are you going to do something about it?
Photo of a k

a k

  • 6 Posts
  • 1 Reply Like
These:

"There are still ways to hide or deselect the shape path:

-Command/Ctrl-H (or View > Show > Target Path) will toggle the visibility of the shape path.

-Enter/Return will toggle the selection of the shape path.

-Clicking on the shape path thumbnail in the Properties panel will toggle the selection of the shape path.

-Esc will deselect the shape path."

are not solutions.
Photo of JEREMY SALLEE

JEREMY SALLEE

  • 11 Posts
  • 1 Reply Like
Really Chris?? You are a photoshop employee and you come with that type of answer to the users

I'm dreaming here. I really though this was a support site. Instead of coming with a concrete answer you come and tell us we are just losing our time? Wow, you might be a great Sr. Computer Scientist but unfortunatelly communication doesn't seem to be your best asset...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
We know about the problem and are working on it.
That's all we can say.
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
"Thats all you WILL say", Chris. Theres a big difference between CAN and WILL.
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
...wait a minute. "Working on it"? So all these "dozens of other places" you mention are not actually SOLUTIONS, just more talk?

Dude...maybe you could have just posted this information first (about 20 comments ago) and saved us all some time and angst. I really don't understand your reticence/apathy here...or your tone.
Photo of a k

a k

  • 6 Posts
  • 1 Reply Like
^ I agree. That's a bit arrogant.
Photo of Nicholas Terry

Nicholas Terry

  • 5 Posts
  • 1 Reply Like
Thanks for the response Chris. We have seen that this problem has been marked 'Acknowledged', but it has been not stated here that it is being worked on. And in this forum there has been no response from Adobe or an employee. The only responses for this have been 'work arounds' and the sentiment that we have received is that this is a 'nonissue'. The other places that mention this as an issue are the PS6 Beta forums that no longer allow commenting on. Doing a google search for this problem shows the PS6 Beta forums and not this page. Its actually a bit hard to find this forum.

I think we all know that the squeaky wheel gets the oil and we want to make sure that this issue is actually being worked on. When more people know about issues, and how much they affect people, priorities can and do get shifted. I am sure that there are many other designers who have this issue and are either unaware of this forum, not active online on this forum, or have yet to upgrade to CS6.

We all love Adobe products as they empower us to communicate in ways no other products can. As designers, working with Adobe products everyday, we have workflows with your products that we have come to know and rely on to be able to work as efficiently as possible. This is why people here are so passionate about this issue; vector shapes in Photoshop is a major part of all of our workflows. Whether it be making 'shapes' or creating vector masks on current layers (see my previous comment for vector mask creation issues), the previous workflow created the least amount of friction to working with vectors. Changes to how vectors are treated has created a few additional key strokes or clicks every single time that you create/manipulate a vector. When you are working on a document with a lot of vectors or shapes, just even one more keystroke compounds into an incredible amount of time (let alone clicking 3 times on the interface to add a shape to a newly created vector mask). When this time is multiplied by the amount of people who have to work around this issue, countless hours add up.

All of us realize that these new workflows (or work arounds) add up to an incredible amount of time, so we are being vocal about it. Any more eyeballs and voices on this issue is a good thing to show how important this issue is. This issue may currently be marked as a "feature enhancement" on your internal system as its not detrimental. But to us it is an actual "bug" and is detrimental to our workflows. It should likely have a higher priority than other items in the queue that affect far fewer people. We are not able to see your current bug / feature enhancement list and do not know where this ranks on the list of things and how many resources you have dedicated to solving this issue. So coming from the outside, any additional noise to ensure that this is as high as possible, with as many resources as possible is the best thing that we can do.

Thanks again Chris for responding in this particular forum that is accepting comments. We have all been feeling we are talking to a brick wall.
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
Well said Nicholas!
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
May I just point out that Nicholas did NOT have to be so kind in his appraisal of Chris's minimal involvement in this thread, and stroking Adobe's ego about their products is a nice gesture but will not invite better customer service and technical support.

Not just a brick wall, but one with all the wrong signage.
Photo of Brandon Tyson

Brandon Tyson

  • 37 Posts
  • 4 Reply Likes
Here's an example of both Chris and Jeffrey actually making a service-driven response to a problem:

http://feedback.photoshop.com/photosh...
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
hmm, not much of an improvement IHMO but better than we have on here.

Jeff was pretty quick on it & seems positive but no follow up to actually help, but Credit of sorts to Mr Cox who followed up 2 months later with a sort of workaround but no follow up for a proper fix. Hasnt impressed me much considering this is a forum to resolve and not just acknowledge problems.

Again, 3 months later and no fix for that problem either other than switching something off.

Expected much better to be honest.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
There were a dozen topics about the same issue, and we covered the workaround in most of them. And a fix has to come in code, but we were able to find a workaround (turning off layer thumbnails) until we can get a fix ready.

But fixing bugs and testing the fixes takes a longer than you seem to realize. Also, we'd really like to fix most of the bugs at once rather than putting out a fix at a time (which would make the process take a LOT longer).
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
We don't question how long actual code fixes take, only how long it took for someone to respond to _this_ thread.

Obviously most of us had no idea there were "a dozen topics about the same issue" or that "we covered the workaround in most of them". For my part, I did search the forum for this issue and found nothing matching my query but this one (just think how one needs to phrase the query). So perhaps better disambiguation on user queries for product bugs than just responding to a few threads and ignoring others.

(Alternatively, threads themselves could be made to work like bug reports and be wrapped into one another as needed if duplicates arise; this is old technology.)
Photo of Tony Gines

Tony Gines

  • 6 Posts
  • 0 Reply Likes
Here's one of the "multiple discussions". It's on their forums but is read-only so we can't update it.

Jeanne Rubbo responded saying they did this on purpose:
http://forums.adobe.com/message/42932...

This is not an "issue" to them. They deliberately changed this behavior thinking it would improve workflow somehow. This probably won't change. Just get used to feverishly hitting Enter, or cmd+shift+H all the time.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
Yes, the UI (sorry, "XD") designers wanted it to work that way. That does not mean that people who actually use the product agree with that design.

Again: we are working on it.
Photo of Brandon Tyson

Brandon Tyson

  • 37 Posts
  • 4 Reply Likes
Thanks, Chris. Your last sentence above indicates the perspective we're all wanting to hear from you guys – that you don't intend to force something down our throats whether it was by design or not. I'll shut up now and look forward to the update that contains the fix.
Photo of jordan grosz

jordan grosz

  • 23 Posts
  • 0 Reply Likes
ctrl+Shift+H or cmd+shift+H should be working like a toggle turning it vector paths on or off for all layers so you should not need to be hitting it feverishly.

The only time i have had the paths pop back up after hiding and unhiding a layer.

I really gotta ask if you actually had tried using this short cut before ranting on about how many billions of extra keystrokes this will add.
Photo of Brandon Tyson

Brandon Tyson

  • 37 Posts
  • 4 Reply Likes
You're lucky you and I are not in the same room. Do you realize that everyone on this thread gets an email every time you post the same ignorant comment? Again I will say, if this wasn't a problem, all the professionals whose intelligence you are insulting would not be here complaining.

Shut up and go away.
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
Jeffrey Tranberry contacted me on twitter and indicated that the yellow "acknowledged" flag was up as soon as this was posted. Don't know, since I wasn't here 3 months ago, but if that's the case then evidently the feedback system needs some mechanism to link related issues (just like a software bug reporting system) so that people aren't sitting around waiting for a response when all the action is happening on some other thread(s)...according to Chris, anyway.

Obviously the dozen or so people following this--including myself--were blissfully unaware of an "acknowledged" flag, hence our frustration.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 842 Reply Likes
We try to merge like topics, but we're not perfect.
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
Then we're all in agreement ;) Thanks for taking the time to keep us apprised; I hope you appreciate the role we play as much as we appreciate yours.

We are, after all, the only reason Adobe exists.
Photo of Nejc Lavrič Osrajnik

Nejc Lavrič Osrajnik

  • 1 Post
  • 0 Reply Likes
I've found another way that works fine for me:
Enable "Show Transform Controls" when in the Move Tool mode and disable Target Path by hitting ctrl+shift+h. This way you'll see the shape element selected and transform controls will disappear after layer styles are toggled.

Hope this helps,
Nejc
Photo of Dave Jennings

Dave Jennings

  • 35 Posts
  • 3 Reply Likes
Good idea and works well if you need transform controls visible but if not then you're stuck with the transform handles now instead.
Photo of Brandon Tyson

Brandon Tyson

  • 37 Posts
  • 4 Reply Likes
That's still additional keystrokes, and it only helps with setting layer styles. About 10,000 times a day, I turn a layer on/off/on/off/on/off quickly in order to see before and after I've made a change. Since the path becomes highlighted again when the layer is shown, it's now impossible for me to see this A/B comparison of changes.
Photo of jordan grosz

jordan grosz

  • 23 Posts
  • 0 Reply Likes
just use ctrl+shift+H without transform control turned on.
You don't have to keep hitting it over and over it toggles on and off so if you select another tool or layer and come back it still will not be showing. Also you don't need to do this per layer it is universal so if you select one shape layer and toggle the vector path off then select another vector layer then it will be still off.

The only time this turns back on that i have come across is if you hide a vector layer then unhide the layer. At that point it defaults back to showing the path but just hit cntrl+shift+H again and your good.
Photo of Brandon Tyson

Brandon Tyson

  • 37 Posts
  • 4 Reply Likes
As stated above: "About 10,000 times a day, I turn a layer on/off/on/off/on/off quickly in order to see before and after I've made a change."
Photo of jordan grosz

jordan grosz

  • 23 Posts
  • 0 Reply Likes
@ Brandon

Ok so would this work in your case?

make a blank layer either at the top of the stack or whatever. After you have the vectors paths turned off then if you are toggeling a layer on and off just select your blank layer first. I have noticed it only reverts back if you have the layer you are toggeling on and off selected but that doesn't happen if you have another non vector layer selected. That way when you want to check your work just select the blank layer and then toggle on and off the layers you want to look at.

It's still a bit annoying but until Adobe fixes it then that might be quicker for you.
Photo of OJ

OJ

  • 19 Posts
  • 1 Reply Like
So I'm still waiting for a fix. Our entire team bought CS6, and no one uses it. Everyone has moved back to CS5.

Does Adobe have any estimates on a timeline here? We've paid for 6 licenses we can't use.
Photo of jordan grosz

jordan grosz

  • 23 Posts
  • 0 Reply Likes
just use ctrl+shift+H without transform control turned on.
You don't have to keep hitting it over and over it toggles on and off so if you select another tool or layer and come back it still will not be showing. Also you don't need to do this per layer it is universal so if you select one shape layer and toggle the vector path off then select another vector layer then it will be still off.

The only time this turns back on that i have come across is if you hide a vector layer then unhide the layer. At that point it defaults back to showing the path but just hit cntrl+shift+H again and your good.

its cmd+shift+H on mac. I stated in some above posts option shift H but it's is cmd
Photo of Emlyn Addison

Emlyn Addison

  • 9 Posts
  • 0 Reply Likes
FYI: Folks from Adobe did already weigh in on this...uh, perplexing "update" to their flagship product. The yellow "Acknowledge" button atop this thread is their signal that it's OK to spend hundreds of dollars on a license because, now that we've all stopped and taken the time to point out the maddeningly daft effect of their development decision on workflow, they're "on it" full steam ahead.

I've said it before but perhaps it needs saying again: Adobe Photoshop developers, what were you thinking?

The mind boggles.