You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fact, I just have did some research by myself. I render each html in background, Then get the total pages. It not a perfect method, but it do work, hardly. I'm still waiting for the official implementation by Readium. I'm glad to have some discussion when they ready to do this.
If you choose my way, there are some thing you should notice.
webView may stop the rendering job at some time. But I don't know the reason.
the timing of html finish loaded, is hard to catch. (Maybe I choose the wrong way, I firstly try KVO of scrollview's contentSize. It sometimes may not much accuracy.)
simply load the html will take much time. Specially when you load some custom fonts.
any font family/size change can make the page change. you should recounting.
you may want to setup a database to save the pages.
Basically you can get the current position index from the last broadcasted Locator.locations.position, and the total number of positions is available with Publication.positionList.count.
No description provided.
The text was updated successfully, but these errors were encountered: