Alt-tab to switch away and back seems to work like escape, when it happens. ... View more

Two years later, and (removed) corporate bureaucracy still hasn't addressed this.       (Please follow the community guidelines to be kind and respectful or risk being banned from the forums.)     ... View more

Yes, Adobe is a huge, soulless corporation whose faceless bureaucrats make these arbitrary decisions, probably by committee, without any consideration for the users. While I'm so used to Photoshop that I still refer to it when in a hurry, I increasingly use alternatives for my work. ... View more

He said "an undo control", ergo he was saying it's one of the controls, the one that redoes it, yes.   ... View more

Why do other programs seem to be able to render  ⍼ regardless of font? Including, for example, whatever browser you're using to read this right now.   ... View more

None of those links lead to the Middle East Language Pack. ... View more

^This is wrong. Dunno if it was partially correct in 2009, but it probably was not, and it's definitely wrong now. The problem is definitely Photoshop.  For example, I'm wanting to use this Unicode character, the Angzarr:  ⍼ You can see it just fine, here, using (checks style sheet) Adobe Clean Serif. But  I try to use it in Photoshop, pasting it in just as I did above, and I get an [X] symbol, in Adobe Clean Serif and every other of the hundreds of fonts I have installed.  I go to https://wordmark.it — a website that shows text in all fonts on your system. I check there: Most of my fonts show ⍼ just fine.  But the EXACT same font, in Photoshop, gives me the square X placeholder. Either Photoshop ITSELF cannot show it, or in order to show it I can't simply paste it in the way I'm doing here in Chrome, and elsewhere, but must go through some needlessly obscure special effort that I'm unaware of. I can't use the Glyphs panel, because it only provides a subset of glyphs that some genius bureaucrat at Adobe decided were the only ones I'll ever need. And what I need is ⍼   ... View more

I'd like to know this, too. It seems absolutely idiotic that if you pick mp4 as the Format, you're suddenly only given 3gp as the Preset. Why the hell do we have to choose H.264 for the format, in order to then have the preset defaulting to various resolutions in the mp4 format...without anything even saying it's mp4?     ... View more

It can only replace whole words. By @Bernd Alheit I want to point out how absolutely idiotic that is. Good gods, do they really not comprehend that we are going to inevitably want to search and replace substrings? Why even impose this kind of nonsensical restriction in the first place? ... View more

@Sonserae Why is it with every update, Photoshop takes away essential tools I use everyday?  My theory is that this is the norm in the ugliness of corporate culture. I've been making a list of bizarre reduction of features in various corporate products. Gmail eliminated the ability to right click on an attached image to copy it.  YouTube removed the ability of channels to annotate videos Likewise, they hid the count of downvotes on comments Speaking of which, Amazon eliminated the ability to downvote reviews...so now the top reviews are often idiotic ones, for example complaining that the post office damaged the package. Other idiots upvote such useless reviews, and the rest of us can do nothing about it. Bank of America has taken features away from their online banking, like the ability to transfer money via their quick menu. Windows randomly resets explorer settings to the defaults, which are clearly better for us than our carefully set up custom settings. SoundHound and Shazam used to check for a song when launched, both disabled that ability even for existing installs. Only Shazam even allows one to manually turn it back on, hidden deep in the settings. eBay now only keeps three years of your purchase history. That you may want to find the name of something you bought five years ago, to buy another, is irrelevant. Chrome disables extensions without asking, because Google decided to.  Adobe decided to explicitly disable pixel line drawing, and a ton of other things in the years before that. Someone should make a list. Really, corporate law has spread the sociopathic, irresponsible culture of the political class to the very businesses that corporatism gives special power over our lives and an oligopoly over the most important industries. It's pretty horrifying. ... View more

You mean Make Pixels Great Again ... View more

They can't "delete it completely", they undoubtedly use some kind of source control like Subversion or Git. So yes, they definitely have the pre-stupid-change code. It may be hard to integrate with their new changes, especially if their code is as poorly organized as I imagine. A well-written program would be modular enough that changes in one spot have little impact on things overall. But that probably isn't Adobe. I mean, they released this change with the stroke set up so that it didn't work at all for existing users until they learned the whole inner/outer thing. Not the brightest knives in the shed. ... View more

Your workaround does not address the problem most of us have with the idiotic removal of the pixel line. We want to be able to quickly click in one spot, then drag the end point to another spot, eyeballing a preview of the finished line, then drop it as pixels. For example, on a layer mask. Your solution of pre-making a bunch of lines in another file is slower and less accurate than actually using the shape line, rasterizing it, and then merging it with the layer where it should have been added. ... View more

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. ... View more

That does indeed sound useful. Can the shapes be broken back down later, as one could do in Illustrator? We don't have the same selection tools, do we?   /me plays around with shapes for a few minutes   Hrm...this isn't working the same as in Illustrator. They don't really merge in the same way. I didn't see a way to grab overlapping pieces and break them away into new objects.   I haven't really tried to do Illustrator-type stuff in Photoshop.    Mainly because I have absolutely no need to. That's what Illustrator is for.   It does sound like it solves your problem, though. It does nothing for my desire to use the line tool in layer masks, but it helps with that perspective trick and similar issues.   People who claim that using a brush, holding shift, then clicking again to make a line don't understand how laughably weak that is. When we use the line tool, we almost always want to be able to drag the line out, then move it around a bit, choosing the exact place for it visually before committing.  ... View more

@JemShaw They certainly COULD have fixed the line tool with this update. Someone else in the thread tried to say Adobe couldn't fix this instantly, but remember that they intentionally broke the line tool. It wasn't a bug, it was a conscious choice on their part. Therefore it should be quite reversible. Add to the list of tasks that any developer with sense would have known they were breaking: Using the line tool in layer masks. This is no longer possible, and is something I was trying to do, yesterday. But you can't add a shape to a layer mask. And, like everyone else here, I don't find the multi-step process of creating a path and stroking it to be an adequate substitute. We professionals care a lot about the time consumed in work, and while this may not seem slow to an Adobe bureaucrat, it adds up. ... View more

I just thought I'd point out yet another way this arrogant, clueless change harms people:   It means you can't use the line tool for a layer mask. Something I had cause to do, today. But could not, thanks to this dunderheaded corporate nitwittery.   Imagine having such tiny minds that the long list of must-be-pixel scenarios presented here didn't occur to them when they were making this decision in the first place. ... View more

@DGrainger  > Google was correctly concerned about being enablers to copywrite theft. That would be the very kind of bureaucratic idiocy I'm talking about. Anyone who wants to can still "steal" copyrighted information, they just have to manually download it first. The only change is that it's immensely inconvenient for those of us who make our living with graphics, who are constantly emailed images to work on, which we could more readily copy and paste than download. Idiocy. Lawyerly nonsense. Your other quote: "And when they are, they should have it slapped out of them by strongly worded criticism." So, you advocate violence when other people's views and interests are not aligned with yours? Are you deranged? Is your reading comprehension so low that you can't understand how "strongly worded criticism" is not advocacy of violence? What the hell is wrong with you? Your own quote refutes your absurd interpretation. ... View more

They might not be able to change things, but they could at least update us and participate with the discussion more often. Again, the rare updates and lack of discussion make us feel unheard. ... View more

@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. ... View more

>  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. ... View more

I skip Budweiser TV ads. That's the benefit of modern TV technologies. There is no excuse for the sheer arrogance of actively taking away features that is so common in corporate development today. If the guys at Adobe are people too, they should learn to act like it. Same with the idiots at Google who actively chose to disable the ability to right click and copy an image in gmail. They think they know better than we do, about when to use a pixel line, when to copy an image without concern for lost resolution, et cetera. Arrogance. "People" shouldn't be arrogant. And when they are, they should have it slapped out of them by strongly worded criticism. ... View more

You keep saying that to people, on this same overall discussion, in cases where it's not clear that they're unaware of it, and probably were saying "you" and "Nice work, Adobe" in a rhetorical way.    Especially since Adobe developers HAVE posted responses on this board, in the past, and it's reasonable to believe that this adobe.com website is sometimes read by developers and others at the company. It certainly should be. If they did not, that would actually show the very indifference and irresponsibility that so many here suspect them of. ... View more

Isn't the latency issue the fault of either Wacom, or the OS maker, or the driver maker?    I'm not seing any real latency issue with my Huion, unless I'm doing something really burdensome like using Smudge in a really complex situation at a high resolution.    Although yes, the smudge tool is horribly handled. There are other graphics programs whose smudge tools do not lag like that. ... View more

I want to emphatically agree with you on line weight/arrowhead.   That was my standard way of quickly making arrows to point to things, and worked great. Being forced to manually change the arrow head's absolute size whenever I am annotating a new pic, because the pics vary wildly in resolution, is intolerable. The necessary change in line thickness for the new resolution solved this whole problem, before. Now I must manually change the arrowhead size separately.  ... View more

Is Sketch an alternative to Photoshop? That's one I haven't tried. I've used Affinity, GIMP, CLIP...I stay longer with them each time the bugginess, instability, and arrogant changes of the last two years drives me away.   Do you mean https://sketch.io/sketchpad/?   ... View more

Saving as a preset is still more trouble than being able to set it as a percentage.   Losing that is an idiotic problem that we haven't emphasized enough on here.  ... View more