Live mask dialog bugs Affinity Photo v2.2.0 (x2 bugs).

[AP-]

1. What Application are you using? Affinity Photo v2.2.0 on macos Ventura 13.5.1.
2. Are you using the latest release version? Yes.
3. Can you reproduce it? Yes. See description below.
4. Does it happen for a new document? Happens in all context, see description below to reproduce.
5. If you cannot provide a sample document then please give an accurate description of the problem for example it should include most of the following:

 

First of all, for a change, really appreciate being able to create, choose, edit, delete a present in one single place (as opposed to adjustments for example).

 

First bug:

Create a live mask (any will do).

Choose a preset (can be one just created on the spot).

Opacity in the dialog shows 1% when loaded irrespective of the value saved, but does not actually apply it. It also does not transfer to the corresponding percentage in the Layers palette (this displays the last valid percentage that was typed in the dialog for the live mask or chosen with the slider).

Expected behaviour: Opacity follows value saved in preset; opacity reflected identically in Layers palette.

 

Second bug:

Create a live mask (luminosity or band-pass).

Type a value in the blue radius. Reverts back to the value on the slider as soon as Enter is pressed or exiting the editbox.

Expected behaviour: Enter or exiting the editbox should validate the value entered not revert to the original value.

[NathanC]

Hi @AP-,

Thanks for detailed steps, the first issue has been logged previously with the developers, so I've bumped the existing issue with your report. The second issue does appear to be new, so I've now logged this with the developers. 🙂

[AP-]

Hello!

Lol.

Please bump it again. The two reported bugs are very much still present in 2.3.0. I would gladly trade you the spiral shape tool for fixing the three or four bugs I've reported in the forum that are still present (since version 1).

They can be reproduced in exactly the same way.

[AP-]

Is it still there in the 2.4.0 beta?

[walt.farrell]

Just now, AP- said:

Is it still there in the 2.4.0 beta?

The Serif Info Bot hasn't posted to say it's fixed, so it probably isn't.

[AP-]

I don't think the bot likes my bugs very much. Who do I need to pay to prioritise my low-impact bugs?

[Affinity Info Bot]

The issue "[macOS] Live Masks- Manually entering a value into the blur radius field and pressing Enter ignores the entered value" (REF: AF-526) has been fixed by the developers in internal build "2.4.0.2222".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[Old Bruce]

@Serif Info Bot, The issue is back in 2.4.0.2279

On 1/9/2024 at 4:15 AM, Serif Info Bot said:

The issue "[macOS] Live Masks- Manually entering a value into the blur radius field and pressing Enter ignores the entered value" (REF: AF-526) has been fixed by the developers in internal build "2.4.0.2222".

 

[AP-]

@Serif Info Bot

Can confirm.

Regression is only in the Luminosity live mask, and only in blur radius. The original bug also affected opacity and the other masks. Have just tried with the three different live masks of 2.4.0.2279.

[EmT]

Thanks @Old Bruce @AP-

I've passed your reports along.

[AP-]

Still there in 2.4.0 beta 2294.

[Affinity Info Bot]

The issue "[macOS] Live Masks- Manually entering a value into the blur radius field and pressing Enter ignores the entered value" (REF: AF-526) has been fixed by the developers in internal build "2.5.5.2589".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Affinity Info Bot to notify us.