P: Pen Tool Not Working as it should

Agreed with *borky that the testing, automated or not - at the very least should be catching and flagging (subsequently preventing a release) ALL nuanced use cases of each tool that has existed within the IDE as of two previous versions. That is the least I expect for having paid out $50/m since 2012.

Which btw, comes out just shy of...

$5,000 !!

First off: I deny any such obsession. 

I know that I have made mistakes in my own work sometimes. 

Luckily those mistakes usually don’t affect as many people as when some individual or team at Adobe makes a comparable blunder within the framework of their jobs. 

So I don’t want to criticize those individuals too harshly just for making mistakes. 

Whether those mistakes are addressed in a timely fashion is naturally another matter. 

And there is another point:

The people who process and assess the Reports and Requests from this site are in all likelihood neither the programming staff that might have introduced/overlooked a bug nor the managing staff that made allocation or strategic decisions that might have contributed to the problems. 

Through the »miracle« of division of labour it seems one is hardly likely to ever directly address the actual person/s one might like to criticise here – so it seems better to try and keep polite …  

@christoph_pfaffenbichler it should've been tested before rolling it out. there shouldn't have to be complicated incoherent work-arounds. stop bootlicking for a company that doesn't give a rats crusty butthole about you.

also, its not very obvious you DONT work for adobe when u defend everything they do. you're paying for a service, they aren't providing it. its as simple as that

• Obviously I do not work for adobe. 

• Obviously we have to wait for, at least, the next Photoshop update. (edit: or roll back the Photoshop version)

With any luck the bug will be fixed there but there are no guarantees about that.

Bug-fixing in a program of the »size« of Photoshop cannot realistically be expected to happen instantaneously. 

And the Adobe employees who might actually know about the time-frame for any specific fixes are not at liberty to make announcements/promises to us here. 

@christoph_pfaffenbichler

why are you so obsessed with defending adobe; a company that doesn't know or care that you exist. to them you are nothing but a source of money.  

Listen here Christoph. There are so many people and businesses that rely on the tools that they are PAYING FOR to work properly. Why should WE have to wait. That's like saying we have to wait months for McDonalds' to give me the fries I paid for. Do you work for Adobe or something?

The work-around has been explained again and again. 

For the actual fix we will have to wait … 

Yes! Absolutely. 

They keep putting new features in, destroying what was there before and what was considered reliable.

Like "frames". I mean: what? There are groups, layers, masks, why would you now need frames, too? Just an example… But the path tool, yea we can live without that. 

Hi, I’ve got the same problem. Please give us a fix!

Ctrl+H is my workaround.  Slows me down a lot.

Adobe engineers, we are losing money we use to pay YOUR subscription.  Why took so long (more than a month) to fix this?  Instead on bloating the software with help features.  You should focus on stability and fast bug solving.