(1.5.0.14) Pixel selection - No marching ants around the shape that is being substracted from existing selection

[Matej Junk]

Hi,

 

Pixel selection - No marching ants around the shape that is being substracted from existing selection.

 

Regards,

 

Matej

[Alfred]

Confirmed here, Matej. The 'Intersect' option behaves the same way.

[Matej Junk]

Tanks for the supplement.  :)

[Chris B]

Hi guys,

 

I tried this in PhotoPlus and we get an outline as we draw so we get some indication as to what the subtraction will look like but it doesn't update it live (as we are dragging). I tried it in PS and we do get the marching ants.

I'm not sure if this is a bug or just how we do it as three apps have slightly different behaviour. It's probably more of an improvement... I'll log it with dev as an improvement and they may leave it or they may consider it to be a bug.

Thanks.

[Mark Ingram]

If I make a pixel selection, then hold down ALT to subtract from that, I see marching ants. When I let go, the marching ants displays around the new shape too. What are you seeing? I'll try to record a video shortly.

[Alfred]

If I make a pixel selection, I see marching ants around that selection. If I add to the selection by pressing the 'Add' button on the Context toolbar before I drag, I see marching ants around both the original selection and the additional one. (The hintline tells me that I can use Drag + \ to add, but if I try to do that the cursor stops dead in its tracks.)

 

If I subtract from the selection (either by holding down Alt or by pressing the 'Subtract' button on the Context toolbar) I only see marching ants around the modified selection, not around the shape that I'm subtracting from it. It's even worse if I want to intersect with the selection, because I'm working blind until the new selection begins to intersect with the existing one. I regard this as a bug.

[Mark Ingram]

Yes, sorry, after I posted that I realised what you were talking about. As this is the same as the macOS version, I'm not going to class this as a bug, however we can look at improving it in the future. Currently it just shows you the result of intersecting the original selection.