go to page... / enter page... menue item doesn't work (?) and inconveniences

[jweitzel]

Whe you are typesetting whole books with AFPub, you will need the menue items/shortcuts for "next page", "previous page" and "got to page..." very often.

If I'm right, the menue item "go to page ..." does not do anything, at least on my AFPub setup on Mac Studio with Ventura.
It just doesn't do anything, just closing the dialogue.

Am I doing or seeing something wrong? Normally, if I want to navigate to e.g. page 128, I would call that menue item and type in: 128, then <enter> and here we go.

There are also two inconveniences at that dioalogue:
• the input cursor in that dialogue should set to the input field of the page number wanted, when the dialogue is opened
• the button "ok" should aktivated, so that by pressing <enter> the action is executed.

(At the moment one can call that dialogue only with mouse (!); you have to press a <tab> or mouse action to activate the input field (!!), you have to use the mouse again, to commit that action(!!!)).

Johannes

(I'm happy with my Affinity Suite)

 

 

[MikeTO]

Hi Johannes, this is a known bug in v2. In the meantime, you can go to page by using the first/previous/goto/next/last page controls at the bottom left of the screen or by using the Pages panel.

 

[jweitzel]

Oh, I'm sorry. I did a search for "go to page" (I'm working on a German version of AFPub) and didn't find anything really related.

Thanks for your hint!

Do we hope, they will spike the other two aspects, too....

[NathanC]

Hey @jweitzel,

This has now been fixed as of the 2.1 Beta if you want to try to 'Go to Page' function. 🙂

https://affinity.serif.com/en-gb/affinity-beta-program/

[jweitzel]

Many thanks, Nathan (what a nice/wise name!) for your information!

I prefer to wait for the final release. My work is much to responsible (?) as to experiment with betas.

Johannes

(I'm happy with my Affinity Suite)

[Affinity Info Bot]

The issue "Document > Go To Page... fails" (REF: AFB-7104) has now been fixed by the developers.
This fix is included in build 2.1.0.1706 (or later) which is already available as a customer beta and will be included in the next 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.

[jweitzel]

Thanks a lot for your valuable hint!
But as I elsewhere stated, I'm working in a production environment, and there even new official updates are somewhat "dangerous" and I use to wait some time whether there may show new critical bugs...

I 'll exercise patience 🙂

Johannes