Skip to main content
Participating Frequently
October 8, 2012

P: CS6 Wrong font-size displaying when selecting multiple text layers

  • October 8, 2012
  • 34 replies
  • 1329 views

When selecting several text layers, then switching to the text tool, the font-size displayed in the upper menu is wrong. It's usually more (last time it displayed 36pt, but both the layers were text composed in 14,3pt)
I can provide psd for further investigation.

This topic has been closed for replies.

34 replies

Participating Frequently
December 19, 2013
David, are you asking about Paul's code? Follow his link. In the left column, click on the "Snippets" section and then click on "Font Size".
Participating Frequently
December 19, 2013
Thanks Paul! I've managed to retrofit my script with your snippet as you described.
Paul Riggott
Inspiring
November 28, 2013
Have a look at the "Snippets" section for "Font Size" @
http://www.ps-bridge-scripts.talktalk...
What you need to do is get the font size, do what you need to do then set the font size again.
It is a total mess!
Participant
November 28, 2013
Any chance you can make that link available again? I think I might need that code.
Paul Riggott
Inspiring
November 24, 2013
Try this on transformed text layers Jeremy...
http://www.ps-bridge-scripts.talktalk...
Participating Frequently
November 22, 2013
This not just *a bug* in CS6, but a *regression* from previous versions of Photoshop. You really ought to make this right by customers who have "upgraded" from CS5 to CS6 (our entire design team of 80).
Participating Frequently
November 22, 2013
This CS6 bug is messing up many of my JSX scripts that do anything with these text layers. For instance, I have one script that snaps the XY position of text layers to a whole pixel coordinate. When I run it, the text size goes back to its pre-transformed size.

This script, and others that manipulate text layers, work in PS CS5 but no longer work consistently in CS6 due to this bug. I see that Paul Riggott has endeavored to explore limited workarounds to this problem (thanks Paul).

Here is my JSX function I mentioned above that I use to snap text layers to the nearest pixel, which does not work on transformed text layers:



function snapTextLayer() {
var textLayer = app.activeDocument.activeLayer;
if(textLayer.kind != LayerKind.TEXT) return;
textLayer.textItem.position = Array( Math.round(textLayer.textItem.position[0].value), Math.round(textLayer.textItem.position[1].value));
};
David Mohr
Participating Frequently
October 22, 2013
Hi guys,

One person's bug is another person's feature...although, as I said, it would be silly to defend the current model.

Unfortunately, I can't publicly comment on what's under development, other than what I've already shared. I can tell you that we have several enhancements underway and I'm hoping they address some of your issues. I can further acknowledge that we're doing another dot-release of CS6 which targets many of the existing type-orient CC fixes. Further, if you're interested, I can invite you to join the CS6 prerelease program for those particular fixes.

Now, if you or anyone reading this thread has bugs related to text and typography, internationalization, translations, foreign language support, keyboard shortcuts and support, or even metadata, please DO go ahead and share those issues in their own threads on this site. I read such topics and I will do my best to raise awareness of your problems. I cannot, of course, promise anything, but I am interested in hearing your perspectives on what works and what doesn't and where possible fixing things. Some issues which you might think we're aware of might actually be unknown to us. Or, we might think the problem is isolated when it's actually common.

This is where feedback from our users is really powerful. It helps us prioritize features vs. bugs and evaluate how important specific issues are.

Thanks and have a good one,
David
Inspiring
October 22, 2013
David, I agree with all of what you said. The thing is Photoshop never was a layout tool nor a webdesign tool, it became such by the actual usage. Adobe is not ackownledging that proprely, otherwise you wouldn't have to take some of your own time to help them focus on the fixes and features that are far from the "photo" editing scope.
What we, creative crowd of all fields, need is a tool that is made, from the start, in our era of all-html designs, not a stitched tool with a long overdue list of features, bugs and long awaited fixes.
The fact that Adobe did provide the update for CC and not CS6 just makes me mad and show how twisted their view of customer care is.
Hopefully, soon enough, a new kind of tool will emerge, but i honnestly doubt it will have the Adobe label on it.
To finish, I have been using Photoshop since version CS 2, and I don't remember having phony information about text size. For me, the trouble started with CS6, but I'm curious of having other people feedbacks.
Thanks for your time David, you may be our only link to get attention from the company we have been feeding for years.
Cheers
Nicholas
Participating Frequently
October 22, 2013
Point taken, apologies for taking my anger at the machine that is Adobe on you. I know you're only doing your job, unfortunately you guys are the only faces that we can see/speak to so you're bound to get a few annoyed people coming at you. S'pose you need a mixture of a*s holes and polite people to generate that hustle and urgency to show the major/not so major problems to eventually make a better product in the end... But yes, once again, point taken, I'll try and be a little more understanding.

Unless you're talking about fixing this problem and adding some other FURTHER feature(s) (ie. listing ALL text sizes on all selected layers (?) ) I'm not sure I agree with you saying showing the correct size of transformed text is a feature enhancement. Fixing something that should be working in the first place surely isn't an enhancement or feature.

Either way, glad it's being fixed. It's just annoying people have to put up with these small but annoying bugs 100+ times day that affect workflow speed only for them to be resolved with a whole new costly version of CS. The small stuff that dramatically affects workflow never ever seem to be fixed.

Anyways, once again apologies for getting on my soapbox and appreciate you taking the time to talk to your users.