P: CS6 program error from vector tools, multiple text layer font size weirdness

This "feature" is not very apparent when you first start using the program as well. It took me a few days figure out the problem. I first thought it was a bug and something that shouldn't be happening.

I agree with the majority here: this change is confusing and not helpful. I think either having the option to use the old way vs the new way is the best, as I can see a use for both.

When you're working to deliver assets for an eCommerce advertising campaign however, often they have specific font sizes that you must use and require several sizes of banners be created. It's incredibly frustrating not being able to drag my layers from one file and put them in the other, resize, then adjust font sizes to be the approved ones. As others have said it's slowing down my workflow. In addition, if we get assets from outside sources, and they have applied transformations (in any version of Photoshop, not just in CS6), there is no way to tell that those text layers have been transformed other than attempting to change the font size of multiple layers at once. I just spent the last 2 hours manually changing the font size on 48 layers of transformed text from a freelance designer; a process that would have taken 2 minutes in previous versions.

In addition, I feel that saying "we didn't get negative feedback on this feature in beta" seems a bit of a lame duck excuse. Many professionals are unable to beta test in their work environment because of either employer restraints on installing software or because of the potential danger of data loss/corruption that is always present when beta testing programs. To say that you didn't get negative feedback during that testing phase implies that the people who paid for the final version of the program are either SOL or should have been involved in the beta testing directly. I know that's not how you intended it, but that's how it seemed to me.

Thank you for your time in not only creating, maintaining and enhancing this amazing product, but also in responding to customer issues and queries. It's incredibly difficult to do both. Thank you again!

I'm sure you are working hard to come up with great updates but this update doesn't make sense guys...
Please give us updates on when this will be fixed, fonts are a major elements in photoshop and allot of time is wasted trying to deal with this.

I'm sure you are working hard to come up with great updates but this update doesn't make sense guys...
Please give us updates on when this will be fixed, fonts are a major elements in photoshop and allot of time is wasted trying to deal with this.

I think that in most Layouts a precise font-size is needed - and "the old way" is the better way to change it fast and precisely.

"The new way" does only make sense, if one wants to maintain the relative size of two or more texts - but in this case I think most people would rather transform the texts together than set a new size by numbers, which is not really intuitive.

Thank you for thinking about new features and functionalities, but in this particular case:

Thumbs up for the old version!

this is awful - it makes my work flow SO MUCH SLOWER.

Also prefer to old way

2 months passed.. are you guys done looking into it yet?

to further elaborate on this issue, to implement this feature properly (even though i dont want it) we should be able to select a type layer, go into transform mode, and see that it was scaled to 152%. then, at the least, we could reset the transformation on that type layer back to 100% and go from there. again, this would be a very annoying workaround, but a working one (since there is no workaround at the moment). right now, after transforming, the type layer will show 100% as its size on the next transform which in some respects is lying to the user since behind-the-scenes you guys are saying its not.

please please please adobe, change this back to it's pre cs6 behavior. honestly, i cant imagine the team at adobe using photoshop cs6 would be sane after using this feature, its imposible to deal with type correctly with this broken behavior