How to remove - Warning: No pixels are more than 50% selected. The selection edges will not be visible.

[onciest]

Is there a way to completely remove this? Even if you make a selection with a large feather radius it is still feathering it regardless, that selection is just invisible. The people here that are answering it are treating it as an error and the only symptom is to not use a large amount of feather strength and try again. The message is really annoying, as I use frequently I might add. So I was wondering if somebody out there could make a script or help me find one, because google itself is littered with this question, but the "resolved answer" doesn't really do anything or relate to what I am asking.

Any ideas?

I've been dealing with it for years, sure I can deal with it some more, but I just thought it would be fixed down the road, as it is a rather strange bug to leave lying around.

[Stargazer on ARM]

"This thread seems to go all over the place and I don't know what actual problem you're referring to."

It sure does, sorry about that 🙂 And yes you are quite right; I was refering to the original post.

I'm starting to think Adobe PS isn't really intended to be used for this kind of work, so if there is a better way or app that doesn't cut me off from my editing every other second to tell me something I allready know I'll be happy to here about it. I have absolutley no need for that information, nor do most of the people I work with, but some pepople obviously do for some reason.

It's not so much the message, It's just the very tiresome and time consuming nusiance of being cut off from editing by a prompted confirmation lockdown every single time the message pops up, and egods does it pop up every other second or click!

Here is my simple reasoning:

I'm using PS primarily to prepare artwork, drawings, old photographs for high resolution animations in AE, Premeier or Animate, typically 4K-12K wall2wall-projections to "paint" the walls and ceilings of an entire room to create a kind of immersive but historically correct environment.  Fiddling around on a deep zoomed in pixel level (and we do that a lot!) triggers off the warning every other time, and it really breaks the flow in a most annoying kind of way (zero feathering is not an option, we really need our feathering).
 
Again; this is nothing less than extremely annoying and very time consuming. Especially when trying to add or subtract a few extra pixels to fine tune a selection already made with object or quick selection. There is no way of knowing forehand exactly how many pixels PS needs to consider it enough for a selection/deselection, so it’s basically trial and error until just the right amount is captured. Now and then PS drops the pre-selected area for no reason, command-zedding or stepping back in history usually but not always gets it back, and so on and so on and so on…
 
Not everyone is using Photoshop this way, but then again a lot of people do. By the way, I have been using Photoshop for some 30 years now and most of the apps in the CC suite for about 10. I wouldn’t present myself as a legend, an expert or an advanced user even or anything like that, but I do know my way around the CC block.

Sincerely yours with best wishes and all that,


Stargazer

[c.pfaffenbichler]

Ultimately I concur. 

Not getting any »marching ants« might confuse some people, lead them to assume there is no active selection and then blame their ensuing mistakes on the Photoshop team – so I appreciate a certain reluctance to remove the alert. 

But it is a roadblock, especially in automation if I remember correctly, so there should be a way to avoid it. 

For the time being I guess utilizing Layer Masks wherever they can reasonably replace the use of Selections might provide some relief. 

[Stargazer on ARM]

Probably so, and again; I'm using PS mostly in interaction with AE, Animate or Premiere and probably in a slightly different manner than just plain Photoshop users.

And just for the record:
If there is one thing I really do appreciate it's how integrated all the apps in the CC Suite are and how well they interact and work together simoultanesly in real time, jumping from one to another upgrading the material in comps, scenes and sequences as you are editing in one or the other or all of them at once. I have honestly never seen anything like it in any other bundle of apps, and things like that pretty much weighs up for many of the little annoying thinghs like pop up menues that just won't stop bugging you 😄

And to jane-e:

I probably didn't phrase my question very well: I do know how to start a thread, I do know you can't start a thread within a thread (kind of Edgar Allan Poeish, don't you think? 😄) and I do know how to search a forum. I was merely trying to avoid starting a new and presumably unnecessary thread if someone indeed already started one somewhere within this Community. But most likely not, I would have found it alrerady.

Cheers and have good one 🙂

Stargazer

[jane-e]

Someone suggested starting a new thread  presenting this thing as an idea/suggestion for improvement, but I can't find it. Could someone link me, please? Provided of course there is one...

By @Stargazer on ARM

You cannot start a new thread when you are in a thread.

• Use the breadcrumbs at the top of this thread to go to the main page for Photoshop
• Select Discussion, Idea, or Bug
• Click the big blue button in the upper right corner that says "Post" to start a new thread.

Jane

[Benjamin24961731y5t4]

 I think this thread needs to get back on track to the actual problem that is this interrupts the automation process when using Pshop
Many people create actions that use automated selections:

For example I create complex actions that use selections from channels. I use a red, green, blue or grey channel selections to create layer masks. I am totally aware that if no selection is possible that no selection has been made. What I DO NOT WANT is for my processing droplets to stop, just because Pshop feels it needs to warn me about this each and every time it occurs.
Like I mentioned there are 2 ways to fix this so that all are happy.

1. On the first occurrence of this message add to the warning box a check that says "do not show again"

or even better

2. In preferences ad a "Suppress selection warnings when making selections" checkbox.

It is really such a simple fix, yet we are still getting nowhere with it.

C'mon Adobe really! I mean really, really!

[Stargazer on ARM]

Right!

My original point just for the records: it's not the message, it's the constant interruptions every other second with what seems to be an endless line of confirmation clicks just to move on. A little bit more understanding from the community and the Adobe representatives that different kinds of workflows might cause different kinds of problems would be nice, too 🙂

Stargazer