Skip to main content
Participant
October 20, 2020
Answered

Fixed: Pixels option is greyed out for Line tool Photoshop 22.0

  • October 20, 2020
  • 111 replies
  • 66550 views

I'm liking most of today's update for PShop, thanks Adobe. 

 

But, I went to use the Line Tool (part of the Shape Tools) and the option to draw with pixels is grayed out. I can draw lines with paths and as a shape, but no longer with pixels. The pixels option is available for all the other shapes (square, ellipse, the new triangle, polygon, custom shapes, etc.), so I don't know why it wouldn't work for lines. 

 

Does anyone know what happened? 

 

{Moderator Note: PS-57177}

Correct answer Akash Sharma

Hi All,

 

Good news, the Pixels mode is now back. For more details on adjusting line weight see Create lines and arrows using the Line tool

 

To update Photoshop to 22.3, click "Update" in the Creative Cloud desktop app next to Photoshop. See: More detailed instructions for updating

 

Let us know your feedback!

 

Thanks,

Akash

111 replies

Participant
April 18, 2023

The option to load 22.3 doesn't appear on my CC app, and I can't use the pixels option of the pen tool.

 

jane-e
Community Expert
Community Expert
April 18, 2023
quote

The option to load 22.3 doesn't appear on my CC app, and I can't use the pixels option of the pen tool.

By @arggggggggggggggggggggggg

 

You replied to a thread that started in 2020. Adobe offers the current version (now 24) and the one previous. You might want to start a new thread and include screen shots so we can better assist.

 

Jane

Participating Frequently
March 23, 2021

Thanks for asking this. The answer will go right into my how to draw a line in Photoshop tutorial [link removed] !

Participant
March 18, 2021

Hey 🙂 I found the '1 pixel black line' problem solution. simply click the Aling Edges and it will be only 1 pixel not 2 and  and it will be true black.

 

Participant
March 11, 2021

Thanks for listening to your users, Adobe, by restoring the pixel line tool. 

 

Let this be a lesson.

 

 

Convergnt
Inspiring
March 10, 2021

I'm glad it's back. Thanks, Adobe.

Akash Sharma
Akash SharmaCorrect answer
Legend
March 10, 2021

Hi All,

 

Good news, the Pixels mode is now back. For more details on adjusting line weight see Create lines and arrows using the Line tool

 

To update Photoshop to 22.3, click "Update" in the Creative Cloud desktop app next to Photoshop. See: More detailed instructions for updating

 

Let us know your feedback!

 

Thanks,

Akash

Inspiring
March 10, 2021

Thank you for fixing it! It works perfectly - as before. 

c.pfaffenbichler
Community Expert
Community Expert
March 10, 2021

In Photoshop 22.3.0 this issue appears to be rectified. (But the Pen Tool seems to be afflicted with other issues …) 

Inspiring
March 10, 2021

The line tool works again with the latest update (Thank you Adobe for fixing it).
@  c.pfaffenbichler >   The pen tool seems to work fine as well.

Known Participant
March 4, 2021

This is crazy! Adobe clearly don't understand how we use their products. Seeing how this issue still hasn't been adressed, in spite of numerous replies to this thread, is really bad. I've always considered Adobe as a company in touch with the users, but this issue made me doubt that notion. 

Fix the issue now, plz. 

Participating Frequently
February 22, 2021

It seems because Photoshop now supports stroke on the shape mode of the line tool, that the developers have removed the old 'go to' method most people used to get a line. Though frustratingly the stroke tool is seemingly set to 'inside shape' by default, so anyone using the line tool will have to find the option to change this before they can successfully create a line. If this fix was made by default, a lot of the complaining would disappear. 

KazVorpal
Participating Frequently
February 23, 2021

Yes, and that's a very amateurish development error.

 

1. It almost certainly means that the first time the developer was testing it, the tool didn't work but — having just made the change — he instantly knew to switch it to Outside, and then it worked.

2. Instead of taking the initiative to change it to default to Outside, he then showed it to the Scrum teammate that approves his item in the burndown chart, who responded "but it doesn't work" and he was like "oh, set the line tool to Outside", and the guy was like "oh, okay" and approved the item.

3. At the end of the sprint his manager tested it (one would hope), sent him an IM saying "it doesn't work", and he had to reply "set the stroke to Outside", and the manager said "oh, okay" and was satisfied.

4. At some future point the QA team was testing it, and needed that same explanation. They were told to set the tool to Outside, and for some insane reason they said "oh, okay" and accepted this disastrous quirk without question.

 

FOUR points of failure. 

 

FOUR development steps where any competent professional would have stopped and said "the end user won't know this" and taken some action.

 

A good development team does not take for granted that an explanation was necessary, because that means the user is going to need that explanation.

 

Either you:

1. Fix the damned tool to default to Outside (duh), or
2. Add a new development item to the board for next sprint, called "change line tool to default to Outside even for existing users", or
3. Set up some kind of tooltip/warning to explain to ALL users that they need to manually change it to Outside. And be 100% certain all users will be painfully aware of this exactly when they are first using the line tool. 


I am formatting all of the above steps with the assumption that Adobe is the kind of soulless bureaucracy who went from Waterfall development to the mindless, faux-agile bureaucracy of something like Scrum, ergo all the crap about adding items and having peoeple approve the mistake. Such a bad development environment does not encourage the creativity and initiative necessary for a developer to simply do things right, like with this line tool. He tends instead to do what he's told without question, his primary concern being to cover his ass. Same with the scrum teammates, manager, and QA. The bureaucrats in charge like this horrible environment of blind obedience, because it makes the blame game easier to play.

 

And that's how they ended up in the situation you describe.

 

Hmmm...

"Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied."

I don't know why I'd've expected Adobe to install a third party message board for their "community" that worked well. All I did was use the WYSIWYG tool to format the above message. I typed no HTML of my own. But it's so poorly made that it managed to break its own HTML insertion. I hope I'm not overlooking some subsequent change that makes my post harder to read. 

 

Oh, and now it won't let me save the post, even after it ostensibly removed the offending HTML it had inserted in the first place. The Post button simply does nothing, it doesn't even reiterate the warning.

 

I'm going to have to paste this into an editor that lets me see the underlying code, and fix it myself.

Okay, nth try at saving this, now with all formatting stripped out.

If this saves, it'll be another grand example of Adobe not even being able to handle a simple user-oriented graphics task.

Participant
February 19, 2021

I solved it...by installing Clip Studio Paint! The pen/ stroke method adds several steps to what was a simple drag and drop, and sadly with dire results (wobbly af lines). It just wasn't good enough for the pixel art I needed to do.

Participating Frequently
February 19, 2021

I've been using it and love it. Maybe it was the brush you were using? I believe you can import PS brushes into Clip Studio.