"Add Master" dialogue box. Typed in Name: vanishes if switch between spread and page.

[GuyMiklos]

Title says it all.

[MikeTO]

I can't duplicate this on Ventura with any combination of dark and light modes, default and large UI fonts, and automatic and custom master names. Perhaps somebody else can try to duplicate it on another version of macOS.

It might also be good if you could include a screen recording since this might not be easy to duplicate.

Cheers

[Old Bruce]

2 hours ago, GuyMiklos said:

Title says it all.

I see this happening only if I change nothing other than the Page / Spread after typing in the name. In other words if I change something in the Margins then change the Spread to Page the name is still there. But sometimes if I then toggle the Page / Spread again the name will disappear.

Mac OS 11.7

[MikeTO]

7 minutes ago, Old Bruce said:

I see this happening only if I change nothing other than the Page / Spread after typing in the name. In other words if I change something in the Margins then change the Spread to Page the name is still there. But sometimes if I then toggle the Page / Spread again the name will disappear.

Mac OS 11.7

Thanks Bruce for confirming this is a bug with certain versions of macOS. I can't duplicate it on Ventura if I follow your steps.

[NathanC]

Hi @GuyMiklos,

I've now replicated the issue and it has been logged with the developers, many thanks.

 

On 12/28/2022 at 4:33 PM, MikeTO said:

Thanks Bruce for confirming this is a bug with certain versions of macOS. I can't duplicate it on Ventura if I follow your steps.

Strange, I was able to replicate this on the latest Ventura 🤔

[MikeTO]

48 minutes ago, NathanC said:

Strange, I was able to replicate this on the latest Ventura 🤔

Odd, I tried it again and still couldn't replicate it, I must be missing something. But it doesn't matter if you've been able to.

[Affinity Info Bot]

The issue "Add Master Menu - Entering a Name and then switching between spread/page clears the name field" (REF: AFB-7169) has been fixed by the developers in internal build "2.2.0.1857".
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.