https://bugs.kde.org/show_bug.cgi?id=422905
--- Comment #5 from Vitamorus <[email protected]> --- I'm not sure I would like the selection to outline only appear around 100% or >50% opaque pixels while more is being selected. It seems even more confusing to me. The border of the selection is a useful indication of what pixels are being considered. Imagine a case where a user has a layer full of only semi-transparent pixels, like an occlusion shadow pass or some subtle glow effects. If they used the "select opaque" action, chances are nothing would show and they might think the feature is broken. I've also personally used this feature to detect some stray patches of very transparent pixels that I wanted to erase. > Maybe instead an option to make the selection binary (fully select all > partially selected pixels, or fully deselect them) would help with Tyson's > usecase? This was sort of what I was getting at with the "Select transparent" idea, which would only select 100% transparent pixels and could be inverted to select every non-transparent pixel fully and thus cover all the bases. A checkbox/dialog for "preserve transparency" would also work. Another convoluted solution would be to make the selection outline also render a discrete screentone gradient that corresponds to the transparency of the selection, i suppose? -- You are receiving this mail because: You are watching all bug changes.
