View Single Post
Old 11-03-2011, 11:58 PM   #665
Micah
Bluefire Reader dude
Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.Micah ought to be getting tired of karma fortunes by now.
 
Posts: 329
Karma: 1089156
Join Date: Oct 2010
Location: Seattle
Device: Ipad
Quote:
Originally Posted by DaleDe View Post
I suspect your description is better. It is not the pressure of the swipe but the timing of the swipe. It is possible that the page, or the next page being prepared is complicated and there is a delay registering the event. This could account for what you are seeing.

Dale
Yes, Bluefire is single threaded, and always renders the "next" page (off screen) to try to have it ready for when you are done with the "current" page. When rendering that "off screen" page, we can not trap swipe events. If you are trying to quickly "flip" through pages, you will experience a lag that can be frustrating. And if the timing is "just right" we might register two swipes in that moment between when the next page is "ready" and the transition to the next page is complete.

In the update we are doing right now, we've changed that in PDF view so that you can "swipe" to the next page, and if it is not ready you see a "working" animation . This makes the app feel more responsive. Maybe we should consider doing that for ePub too.
Micah is offline   Reply With Quote