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

having the same issues. very unhappy

I use to have the same error about selecting several text layers and getting a different number of what it suppose to be...

...and I updated my PSCS6 and my OS to Mountain Lion,to see if you fix the bug, well, now the problem is even BIGER, when I select the text layer and pick the text tool I get, let's say, 17pt, then I select the text and it changes to 24! and there's no way to know which size is the "good one"!!!!

This is not serious! Adobe please don't bother to "fix" what is working fine for years, only fix what it's working wrong! Please!

OS: Mountain Lion

So we paid a lot of money for a major bug? Got it

Just want to add +1 that I also prefer the old way of the text sizing.

Hope to see the real update to resolve this issue soon.

Just want to add +1 that I also prefer the old way of the text sizing.

Hope to see the real update to resolve this issue soon.

We are actively working on solving this problem. While I cannot provide an ETA, this is an issue which we will resolve.

Thanks,
David

Please bring the old way of text resizing back, i could use this functionality back as soon as yesterday. I am not sure what the thinking was behind this whole transform change in regards to text, but I seriously can't think of any scenario where this would be even partially useful. This is one of the most frustrating changes that is adding quite a bit of time to my workflow and don't see how this would really benefit anyone in any form.

Hey David, I'm sure none of us meant to be mean or hurtful. You are indeed doing an amazing job, search feature for the layers is amazing for example! We can't only make good things or we will all be flying air powered air planes. And it would take us too long to list all the good improvements you've made so this is why we surely focus on the bad ones ;)

Looking forward to get an update and get back to normal on this issue.

JK.

I would be interested in discussing real world uses regarding workflow. I commented early on and am still reading the email updates on this.

Hi Bluehair,

We hear you. We are actively working on a fix to restore the old functionality of transform. We changed things to deal with a bug and (quite frankly) to render the app MORE logical, but clearly failed to take into account established user workflows. I can't speak for the rest of the team, but I will say "mea culpa" cuz I thought this change was an improvement, pushed for it, and monitored the Beta to see if anyone had a problem.

That last is an important point. I'm sure you can appreciate that it's often difficult to get more than a limited amount of meaningful feedback of features and bugs. Our channels might seem very straight-forward to us, but perhaps they seem Byzantine to others. I am truly open to any and all suggestions for getting meaningful feedback from customers about the product. The Beta program exists as a chance for users to look at what's in the works and say "that's a TERRIBLE idea" cuz, as I'm sure you're aware from your own design experience, it's easy to think your idea really rocks when it doesn't. In the past this "safety net" has worked quite well. Obviously, not in this case.

Along that last point, I and others on the team, are always interested in doing customer visits (virtual or actual) in order to see how people are using the product in the real world, observe workflow, and try to ameliorate bugs. If you or someone else is a big-time text user and are interested, please ping me back. This applies doubly if there's some text-based bug that's really annoying you! 8-)

While I cannot comment on feature or release-dates of versions that are in development, I will say that we have absolutely heard the complaint about transform and are actively working for a solution.

Thanks,
David