> >One possible solution is to get sprite's bottom corner coordinates and > use > >posToChar, but it won't work in this particular case, because posToChar > >returns -1 if used in beginSprite, prepareFrame or such (the events I'm > >looking forward to). > > Well, try it outside of those events then. > Sure, sure, but my point was ... it would be SO much easier if I didn't have to draw the whole sprite on stage before getting a particular value out of it.
> You can also just get the height of the sprite and divide that by the > point size of the text -- that should give you the number of lines on > display. > Yes and no - as I mentioned, the text is wrapping and even if I knew how many lines there were that won't lead me anywhere, 'cause they're not the lines as Director understands a "line". > >This shouldn't be a difficult task, as I consider it as a very basic > text- > >managing -simply to know what part of the text is visible to the user! > > Text management is not particularly easy, it seems -- it's always > been just the other side of facile in Director, anyway. > Yep, and the most weird thing is that Director is lacking some quite obvious functions (as getting the true number of lines in a sprite despite wrapping). Jussi Jokinen Tampere Polytechnic / Finland [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
