enhancient

> So my question is, should we need `FitMode.cover`? If it's not needed, I want to remove it. At least, the meaning of the word "cover" here seems different from...

> And, for facing pages, it does not maintain the existing facing pages requirements, > > * The cover page may be placed on left-side or right-side according to user's...

> * `SinglePagesLayout` is not explain the actual behavior; it may be something like `SequentialPagesLayout` or such. (I use `sequential layout` that was borrowed from ancient Acrobat Reader); So the...

> @enhancient When `_goToXXX` is initiated by non-user action, such as `_goToPage`, `_calcOverscroll` returns value that actually cancels the move. For example, to go to the last page, I should...

@espresso3389 I've had a go at merging in upstream/master and fixed a few small things in the process.

Great! I'll try merging my changes into the latest pdfrx and see how that goes - the _normalizeMatrix function conflicts with enabling boundaries to be exceeded (which is required for...

I'm also taking a look at this at the moment, and yes, boundaryMargin is important to set for the scroll physics to work as it calculates the boundaries using this....

> Another issue, because pdfrx provides several `PdfViewerController.goTo` and of course `PdfViewerController.value` to directly set the transformation matrix, but I cannot figure out how to initiate bouncing back in such...

After a fair bit of effort I've found what I think is a really good solution - more details in this PR https://github.com/espresso3389/pdfrx/pull/366.