Skip to main content
mrbobdobolina
Known Participant
July 7, 2015

P: Photoshop 22.0: Where is Line Weight/Width and Pixels options?

  • July 7, 2015
  • 676 replies
  • 31676 views

I'm having trouble using the Line Tool in PS 22.0.0. 

 

How do I set the width/weight of the line? In PS 21 there was a "Weight" option along the top bar, but I don't see that anymore. Am I missing it? Or did it move? 

 

This might be a separate issue, but the lines I'm drawing are not showing up. I have a fill color and stroke color selected, but when I make a line, I don't see it. I just see a blue outline of where it is... the same that might happen if I made a "path" instead of a "shape." 

 

I just need to make a line with a width/weight of 20px.

This topic has been closed for replies.

676 replies

mrbobdobolina
Known Participant
February 4, 2021

@arconz I laughed out loud at that. 

"We've talked it over and... ... ..."
"Yes? And?"

"We've talked it over and we've decided... ...that you are our users."

Inspiring
February 4, 2021

Over 3 weeks since the fix was "to be released soon". I guess that means any day now, right Mark?

I mean its great that the Ents found employment there after defeating Saruman, but...

mrbobdobolina
Known Participant
February 3, 2021

I agree. Adobe needs to a better communication policy. 

To be fair, they responded, relatively quickly, to the feedback here and I know for a fact some of the users on this site have tested a beta version of PS where the tool works as it should...

We were told in December that a fix was coming, but wouldn't be ready in time for the December update... and now we've heard nothing for a month an a half. 

There has to be a better way for them to keep us updated on the status of these things.

Participating Frequently
February 3, 2021

@Kaz Vorpal 

Actually, this forum is run by Adobe and there are several Adobe staff that both monitor and respond to issues.  What the fora foragers don't understand is that the Adobe people on this place are not decision makers at the levels that could snap a finger and command grant of everyone's wishes. They work very hard as advocates, but they are only part of a very large organization.

Ciellchan
Known Participant
February 3, 2021

I get you, but Adobe needs to acknowledge this issue further, it’s not enough with having a stressed Dev replying every 10 days. This thread has months of people asking and discussing solutions. We need an ETA for this release more than anything. 

KazVorpal
Participating Frequently
February 3, 2021

@DGrainger MLK Jr said that riots are the language of the unheard.

That includes our verbal riots, because Adobe is not communicating with us sufficiently. I'm on threads addressing the line tool on a message board based on the adobe domain name, and one with the photoshop domain name. Both, as I understand it, are run by "volunteers", not staff, but both are sometimes read by Adobe people, and either way they should feel responsible for sites based on their domains, and be interacting with us about these things. 

And yet they're not. We get rare thirdhand mention that someone's working on it, but little better than that.

Hire a minimum wager with social media skills to read these boards, go talk to the developers and the bureaucrats probably meddling with them, and come back to give us an idea of what's going on with regularity. 

It's better than losing us to competitors. Hey, Corel has a raster graphics program like PS too, right? That's one I keep forgetting to try. I mean, Corel Draw used to be pretty decent, though it's been a couple of decades since I messed with it.

j. aaronk67378513
Participating Frequently
February 3, 2021

Being non productive is the very thing we're complaining about.

Participating Frequently
February 3, 2021

@Ciellchan:  I guess I'm seen as selling Buddhism to a Bishop...   Yes, I agree that there is a problem, one which Adobe is scrambling to repair, one that is not as easy as some here have posited. But, I see all of the emotional kvetching as being negativism and non- productive.

KazVorpal
Participating Frequently
February 3, 2021

>  we are all still choosing them despite this issue

Speak for yourself. I've used PS for 29 years, but what it boils down to right now is that, in order to retain me, they need to fix things before I'm sufficiently used to one or more of the alternatives. Intentionally broken nonsense like the line tool, along with overall program instability introduced in the last few years, is pushing me out the door, whether I like it or not.

Each project, I use Photoshop until it gets laggy from memory leaks, crashes from some bug, stops updating the screen properly, or I run into a voluntarily created problem like the line tool. Then I switch to something else — often because I would've had to restart PS anyway — and use that until my unfamiliarity drives me back to PS to get some task(s) done more easily. But each time, I know the other tool a little better, and stick with it a little longer.

Eventually I'll almost accidentally just stay in Affinity, or CLIP, or GIMP...I have four different ones and I'm still rotating between them, trying to decide which combination does everything I need. It'll become normal for me to use them.

All the other guys saying they've had to add Affinity or whatever to their workflow for the line tool or some other reason:

Even if they're not planning on it, they're also getting used to that alternative. Every day Adobe leaves these problems simmering, they're building up a long-term precedent that could seriously damage their company.

Ciellchan
Known Participant
February 3, 2021

I believe you fail to see we pay for a tool, it’s not about point of views is about signed contracts. It’s about fulfilling said contracts. The conversation on this thread is not an exchange of opinion between mutuals, it’s a conversation between customer and client. 

People are not hating on Adobe, we are all still choosing them despite this issue, we are just worried and concerned about the time it’s taken them to resolve this issue.

And to be honest, this is possibly an UX problem, the research and testing were probably done with a non representative customer base,  it can happen. Yet a good communication from Adobe about this matter would be very much appreciated. The devs are doing their best but they can’t be a shield.