Photoshop CC: Scrub text leading jumps the value super high

  • 26
  • Problem
  • Updated 2 years ago
  • Solved
  • (Edited)
When I use the scrub method of adjusting on my leading, PS(win) unexpectedly jumps the number way up, even if I'm scrubbing left, even if i'm holding the alt key.
Photo of raul gomez

raul gomez

  • 9 Posts
  • 0 Reply Likes
  • sad

Posted 6 years ago

  • 26
Photo of Kate Moss

Kate Moss

  • 1 Post
  • 0 Reply Likes
Followed the whole thread and having the same issues with tracking and kerning. I put in "30" for tracking and it gives me "6". Not what I was looking for.

Crossing fingers for a speedy update to CC.

Thanks for all you guys do.
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Official Response
Okay, I can finally post this:

We have made many fixes to the behavior of transformed text and they are now available in the latest release, Photoshop 14.1, which you can download RIGHT NOW. I will acknowledge, there are still a few lingering issues to resolve, but for most users, these fixes should handle their problems. We felt it was better to get a partial fix out now than a perfect fix in the future. We are still planning additional improvements for a coming release.

If you are still struggling with problems, by all means let us know so we can make sure we address them.

Thanks and enjoy!
David
Photo of Gabriel Watkins

Gabriel Watkins

  • 1 Post
  • 0 Reply Likes
Hi David. My Creative Cloud subscription tells me I'm "up to date", but my Photoshop CC version is 14.0. How do I download 14.1?

Best,
Gabe
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Click Help > Updates and you should be automatically led through the process. You can check by going to Help > System Info.

If you continue to have trouble, ping me and I'll set up a screenshare so we can troubleshoot the problem.

Thanks,
David
Photo of Charles Badland

Charles Badland

  • 60 Posts
  • 4 Reply Likes
David-
What about CS6 users? This bug was introduced in a CS6 update. No fix for us?
It looks like Adobe has pulled the CS6 update that contained the bug. What are the steps to "downgrade" Photoshop CS6 to the version before the bug? Is this our only option?
Photo of Amber Creed

Amber Creed

  • 5 Posts
  • 0 Reply Likes
I'm stuck in Photoshop nightmare right now where I went to change text size with the scrubber... then it added at least 1,000 points. Now I'm getting an error message about "A value between 0.01 point and 1296" and every time I hit OK, it jumps to the leading number scrubber and gives the same error (despite leading only being at 132.81). Come on, Adobe.

I'm CS6 too... having this issue for a while with the scrubbed number jumping but the weird error messages just started today. Have had to shut down and lose lots of work 3 times now...
Photo of Amber Creed

Amber Creed

  • 5 Posts
  • 0 Reply Likes
I should add, the error just switches back and forth between text size and leading size. I can't get out of it. Just endlessly hitting okay...
Photo of David

David, Official Rep

  • 2994 Posts
  • 450 Reply Likes
Hi Amber,

Check out the end of the thread for some solutions.

Also, a work-around is to simply not transform type but instead change the point size. Or, if that is too inimical to your workflow, go ahead and make the transformations that you want, note the new point size of the font, and Undo. Afterwards, you can simply change the point size of the font WITHOUT a transformation and the bug will not be triggered.

Thanks,
David
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Hi Charles and everyone else,

Yes, we have not forgotten CS6. We are looking into putting these fixes into an upcoming dot-release for perpetual users. At this time, that's all I can say.

Meanwhile, for those who have switched to CC, the first round of fixes are available today.

Thanks,
David

p.s. -- posting the same complaint in every thread is annoying and sorta childish. It's also SPAM.
Photo of Charles Badland

Charles Badland

  • 60 Posts
  • 4 Reply Likes
"p.s. -- posting the same complaint in every thread is annoying and sorta childish. It's also SPAM."
David, I was simply responding to the identical duplicate posts you had made in numerous threads. My only goal was to make users who were following specific threads aware that this "fix" did not apply to CS6. My intent was not to spam. Sorry if it came across as childish, but realize these fora are so segmented that, as you have demonstrated, duplicate posting may be the best way to get information distributed.

CB
Photo of Geoff Price

Geoff Price

  • 2 Posts
  • 0 Reply Likes
David,

I can't speak for everyone, but I added onto this chain to echo that I was also having this bug, to help Adobe know that it is/was affecting a lot of people. It was a large enough of a stone in my personal workflow that I started an account to log the bug on here with others, and I don't ever do that.

Maybe it wasn't your intent to insult everyone that is trying to help report this bug by calling them childish or spammers, just for saying that they also had this problem in this thread, but that's how that comes off.

I appreciate the bugfix- but maybe be a little bit more sensitive to how you address your end-users.
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Geoff,

First, sorry if my comment seemed offensive. That was not my goal at all.

Second, PLEASE comment on bugs you find and go ahead and echo things so the voices of all users can be heard. It's actually very helpful when getting bugs triaged to know if one person or many are having an issue.

Finally, that said, posting the exact same comment on many threads is NOT helpful and is actually sort of annoying. It just becomes noise that obscures the issue. My ps wasn't in regard to reports of this bug in general and I'm sorry if it seemed that way. I was actually referencing Charles' post asking for a CS6 fix in EACH thread where I had commented that there was a fix available for CC. Some people would delete all the SPAM comments; I would rather simply ask for self-restraint, so that the forums can be of better use to everyone, rather than cluttered with repetitive messages that have been asked elsewhere.

I posted the fix notice to probably 12 or more different threads (here and elsewhere) because users have asked me to do so AND I want to help as many people as possible find a solution. That's a little different that spamming a dozen threads with a specific request.

I am EXTREMELY aware that this bug is causing users loads of problems in both CS6 and CC, which is why the day we had a solution, I proposed these be rolled into a dot-release for CS6 as well. Unfortunately, this has not happened yet, but it is my hope to get these updates available for all users.

Thanks,
David
Photo of Charles Badland

Charles Badland

  • 60 Posts
  • 4 Reply Likes
David,
Please see my above reply to you. My intent was not to spam, but to reply to your repeated posts - to let users know who were only following specific threads that this update did not fix the same bug in CS6. I apologize if my post was offensive to you or any Photoshop.com user. That was not my intention.

And... Any word on a fix for the PDF text corruption bug also introduced in a CS6 update?

Having these two Photoshop CS6 text bugs fixed will make a world of difference to professional users who rely on Photoshop's text capabilities for quality output.
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
We have been working on a solution to these bugs for CS6 as well a for CC. While the transformed type fix for the Creative Cloud is already released, that for CS6 is still being refined.

If you are interested, I would invite you to join a special prerelease program to validate these bugs really are resolved. All you have to do is respond to this message. I will then submit your name and email address to the program. You will need to sign a non-disclosure agreement, since this software is not available to the general public. Then, you can download and tryout the fix for yourself. If we've missed something, your voice can help us catch it and repair it.

Thanks,
David
Photo of adam sibley

adam sibley

  • 3 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled
Option-dragging palette icons in photoshop CC now increases/decreases erratically.


I've just started using Photoshop CC today and have a bee in my bonnet!
In Photoshop CS5 a really quick and user friendly shortcut was option-dragging the icon beside a value in a palette (such as the character pallette), and this would increase or decrease the value as you dragged the mouse. (i.e if you had written some text on the canvas you could increase/decrease font size on the fly by option dragging the 'T' font size icon within the character pallette).
In Photoshop CC on my machine this action now behaves extremely erratically and is no longer is useful because of this! Is this happening for everyone or just me? I'm on a mac OS 10.8.4.

Image below highlights where you can option-dragging to increase/decrease values.

Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 838 Reply Likes
Also, there is no need to option-drag, just click the label and drag.
Photo of adam sibley

adam sibley

  • 3 Posts
  • 0 Reply Likes
Hi Chris,
Just dragging increases in units of 1.
Option-dragging increases in units of 0.1 for higher precision.
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Hi Adam,

The bug is due to transformed type. This problem is fixed in the latest update of CC, 14.1.1. You can download it today.

Thanks,
David
Photo of Greg Sue

Greg Sue

  • 2 Posts
  • 0 Reply Likes
Hi Chris,
Having issues with Photoshop CC ( i have the latest update ). Mac OSX 10.9.2

The paragraph leading is behaving incorrectly.

For a 6pt text, with a leading set to 6pt, it displays a leading closer to 14pt? Other character sizes with other character leading not displaying correctly.

Any clues?

thanks Greg.
Photo of Greg Sue

Greg Sue

  • 2 Posts
  • 0 Reply Likes
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Hi Greg,

I'm not seeing this on Mac.  Are you sure you have the latest update?  Have you transformed this type at some point?

If you would like, we can do a web-hosted screenshare to get to the bottom of your issue, but at this time, I am unable to duplicate what you're seeing.

Thanks,
David
Photo of Fhabio Jarno

Fhabio Jarno

  • 1 Post
  • 0 Reply Likes
Hello David , I just updated my photoshop to the newest one released this week, CC 2018 version and this bug appeared to me. Doesn`t matter the value that I try to type on the keyboard, the paragraph leading just start jumping to high random values, ignoring the numbers that I`m typing. Arrow keys also aren`t working either to setup the value.

update: it seems this bug happens with asian writting, as when I write in Japanese. In normal alphabet,this bug doesn`t happens. May be some conflict with Google IME or MS IME?
(Edited)
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Yeah, this stupid bug came back.  Someone changed something right before ship and retriggered it.  We're working on a solution and know the problem -- the text was transformed at some point and the math involved to display the values correctly is colliding with user input.

If you create new type or work with type that was never transformed, you won't have the problem.

Hopefully, we'll have a fix out very soon.
Photo of Bash Khan

Bash Khan

  • 1 Post
  • 0 Reply Likes
I'm an in-house designer in a very fast paced company. I need to change the leading every 2 seconds and I have to go through  a ridiculous to try and adjust the leading between two lines now. Please fix this bug SOON (my livelihood depends on it!)
Photo of David

David, Official Rep

  • 3104 Posts
  • 483 Reply Likes
Hi Bash,

We are actively working on a fix and understand this bug is a problem for many people's workflows.  As a TEMPORARY workaround, you can either work with the previous version or untransformed type, since this bug is isolated to transformed text and is new to 2018.  I know, not ideal, but it should work as a stop-gap.

Thanks,
David