Brush Outline Cursor disappears during Refine Selection…

[smadell]

This was not a problem in Photo v1, but is a current problem in the latest retail version (2.1.1) and the latest beta version (2.2.0 build 1903) of Affinity Photo. During a Refine Selection operation, the brush outline can be made to revert to an arrow if the user clicks anywhere (I think) other than dirrectly on the image.

Once a selection has been made (I have done this with the Selection Brush and by invoking a selection stored as a Spare Channel) and clicking the Refine button, the cursor appears as a thin round circle which indicates the size of the brush stroke to be used. This is the behavior I am used to, and the one that makes sense. However, if the user clicks anywhere else (for instance, using the mouse to reposition the Refine Selection dialog, which is frequently necessary) the cursor immediately turns into an arrow. The cursor will not respond to resizing commands (such as with the left and right square bracket keys) and there is no indication of the size of the brush stroke to be used. This situation corrects itself once the first mouse click is made on the canvas, but of course by then it's too late. Also, any subsequent mouse click off the image (e.g., to reposition the Refine Selection panel again) once again reverts the cursor to an arrow.

A screenshot video is attached.

My system: Mac Studio with M2 Max, 64 GB RAM, wired Kensington mouse, Apple Studio display, macOS Ventura 13.4

Photo Performance settings: Hardware acceleration OFF, Display set to OpenGL, "Use only integrated GPU" is UN-checked.

 

 

[Callum]

Hi Smadell,

As far as I'm aware this is by design, this also occurs when I try this in V1 as the refine settings dialogue is now in focus. You can revert the cursor to the refine cursor by clicking inside the space along the top of the app or anywhere on canvas etc.

Thanks
C

[Return]

On windows it just returns to the brush size and doesn't get stuck on the mouse pointer.
 

 

 

[smadell]

@Callum Thanks for responding. I never noticed that behavior in version 1 (although I just looked at my copy of v1 and it does, in fact, act that way). I for one much prefer the behavior that @Return demonstrates. Chalk it up to faulty memory, I suppose, but alternating between the arrow cursor (while over the settings dialogue) and the brush cursor (when over the canvas) would certainly be preferable.