Well you should be able to get the metrics of the font and the size of the textview... if you can get all that, then some quick math should tell you how many lines will fit in the view.
- Brill Pappin On Dec 14, 12:36 pm, HippoMan <[email protected]> wrote: > I've already looked at the TextView source, as well as the source of > the Paint object and other objects. I haven't been able to find > anywhere where the data I'm looking for is stored, or at least > returnable. But there are many android objects to look through, and as > I mentioned, I'm trying to avoid reverse engineering a solution for > this (looking through the source and rewriting what is already done > internally) unless there is no easier way to accomplish this. > > Here's what I'm trying to do: > > I want to provide "paging" through a large piece of text, where each > "page" is a screen that contains a subset of the text. This is to > implement something similar to the "page turning" that is done within > e-reader applications. > > I know how to implement the pages and the page-turning, itself > (circular list of screens, event capture, animation, etc.), but the > part that I still need is to determine exactly how much text will fit > into each of these pages. > > As I mentioned, I know I can "re-invent the wheel" and use the brute > force method and calculate this by means of view area, border and > spacing size, font size, etc., and by manually word-wrapping the text, > but if there is already is an easier way to determine how much text to > stick into each page, I would much prefer to use such an existing > method. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
