repeatable UI bug in Guides dialog

[flyleaf]

I've happened upon a UI glitch in the Guides dialog box (View > Guides…).

Steps to reproduce:

1. Create a new file using the Print > Letter preset
2. Go to the Master A spread
3. Select menu option View > Guides… to open the dialog box
4. Create two new horizontal guides at .5" and 8", but do not close the dialog
5. Click the button for a new horizontal guide, then double-click its position to highlight/select it, but then hit ESC (like maybe you decided to not add this guide) — which, oh right, completely closes the dialog box
6. Noticing you still have the unwanted third guide, hit Undo once to remove it
7. Reopen the Guides dialog box
8. Notice the highlighted value for the third guide, which you just removed via undo, is still there, and it is actually obscuring the 8" guide in the list. This highlighted value will persist here for as many times as you close and reopen the Guides dialog, until you actually hit the delete key and click away to stop editing it.
9. If, instead of deleting the value, you simply hit enter to accept the value, then the previously obscured value (8") will be replaced. Definitely an unexpected and destructive behavior.

Step 6 is option to reproduce this bug, but seems to be the step that leads to the more serious consequences. Basically any guide value that is not finished being edited when the dialog closes will stay in its mid-editing state.

• Are you using the latest release version? Yes, v. 2.0.3
• What is your operating system and version? macOS Monterey 12.6

[MikeTO]

I duplicated this bug on Ventura, too.

[loukash]

Can't reproduce on Catalina. The 3rd "floating" input field doesn't obscure or replace anything.

[MikeTO]

Here's a screen recording showing simpler steps to recreate.

 

 

[loukash]

3 hours ago, MikeTO said:

Here's a screen recording showing simpler steps to recreate.

I don't see anything unexpected there.
The input field is a kind of floating temporary UI object. Since the object it originally belonged to – the guide – has been undone, the input field is now "orphaned" and will thus disappear because it has nowhere to go. No harm done.
So perhaps a minor UI glitch at "best". 

[MikeTO]

There's an even simpler set of steps, there's no need to close the dialog since it isn't modal.

1. Open Guides
2. Create a guide
3. Double click the list item to edit it
4. Undo - the item will be removed from the list but the editing control will remain.

[flyleaf]

9 hours ago, loukash said:

I don't see anything unexpected there.
The input field is a kind of floating temporary UI object. Since the object it originally belonged to – the guide – has been undone, the input field is now "orphaned" and will thus disappear because it has nowhere to go. No harm done.
So perhaps a minor UI glitch at "best". 

While I appreciate MikeTO's video, it doesn't demonstrate where this bug gets more confusing and potentially problematic for the user. Following my steps exactly (at least, for me) causes the glitch to float over an existing and desired guide in the list (8" in the example), fully hiding that from view. And if for whatever reason you choose to hit enter in there, the 8" guide goes away. The user won't expect that and may not even notice that they lost it.

loukash, since you are on Catalina, I take it you are on Intel whereas MikeTO and I are on Apple Silicon… perhaps this glitch is only present, or only destructive at least, on Apple Silicon?

[MikeTO]

I'm on Apple Silicon, too. I agree that this is a bug that should be fixed.

[stokerg]

Hi @flyleaf,

Issue replicated and logged  

[Affinity Info Bot]

The issue "Undo adding a Guide removes it from the Page but the entry is still listed in the Guides Manager" (REF: AFB-7233) has been fixed by the developers in internal build "2.1.0.1732".
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.