I'm not trying to get you to do or not do anything. But you're saying x, y, and z are wrong or impossible, yet I'm seeing that they aren't, so I'm giving you my thoughts on those. We can either kick and scream until Apple makes the changes you want or learn how to best work with what we've got at the moment. I'm not really a Books user, so I can appreciate that you have more refined wants/needs than I do for the app, but I have to also adapt when Apple or other developers change (in a way I don't like or am not used to) apps that I DO use heavily. I also submit feedback to the developers just like you've done.
But I do have to press you on one point here. How is this page-turning speed an issue? See my video below. I mean, I simply don't get the complaint.
I never said they were wrong or impossible, just that it's different. I've submitted a few more bug reports today anyway but would also like to discuss these issues with other Books users.
For the page-turning, I think I pin-pointed my issues:
1) in your video I believe you are tapping the right arrow, if you hold and press the right arrow it's slower.
2) the redesign of the page-turning now shows the right side of the book first, where as in Big Sur it would show the left side before advancing.
If I wanted to read a paragraph(s) that split between pages I would need to entirely advance the page in order to complete the passage. If I want to re-read the first part of the paragraph(s), I would entirely turn the page back.
This action now mimics a real book (i.e. if you start turning a page you would see the right page first), where previously it didn't.
In Big Sur if, for e.g., I was reading a cookbook and wanted to refer back to the previous page I could use the trackpad to "half-turn" the page and get both the right side and left side of the book on the same page (while holding the position on the trackpad).
Now in Monterey I need to do full page advances.
So while the
time to advance a page may be the same, the
perceived time of the advance feels longer since I will need to wait the full page turn to continue reading.
Does that clear it up? I'll probably just paste this whole comment into my bug report lol