View Single Post
Old 02-17-2011, 11:02 AM   #7
mikelv
Developer of EPUBReader
mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.mikelv once ate a cherry pie in a record 7 seconds.
 
Posts: 262
Karma: 1922
Join Date: Oct 2009
Device: none
Quote:
Originally Posted by theducks View Post

If you know the number of segments, why not throw up a progress-bar with equal sized segments (stacked bars) and compute the progress for the current segment only when it is open. Prior to that segment it is assumed 0, after it (the segment) is assumed 100. No need to compute all segments at once.

Slightly non-linear display, BUT, That is closer than anything we have on many reader devices
You are right, this could be a pretty easy way to implement it . I'll think about it.
mikelv is offline   Reply With Quote