I'm talking about cutting off ascenders and descenders of text, or cutting off 
partial lines of scrolled text.

I don't see where that's being done, but I'm observing the effects of it. I 
don't think anything in my code is causing that…

On Apr 7, 2014, at 7:52 PM, Alex Harui wrote:

> Without looking, TLF is "width-dependent".  You give a composition width
> and the TextLines are created with just enough stuff in it to fit the
> width.  Then, once you've created enough TextLines to fill the composition
> height, it stops creating more TextLines.
> 
> -Alex
> 
> On 4/7/14 9:45 AM, "Harbs" <harbs.li...@gmail.com> wrote:
> 
>> One thing I'm having trouble figuring out:
>> 
>> What clips text beyond the bounds of the container?
>> 
>> On Apr 6, 2014, at 8:26 PM, Alex Harui wrote:
>> 
>>> I don't know of any.  It would be great if you could document it.
>>> 
>>> On 4/6/14 5:27 AM, "Harbs" <harbs.li...@gmail.com> wrote:
>>> 
>>>> I'm referring more to the composition lifecycle. (i.e. Text is marked
>>>> damaged by x, Class y is called to start compostion by y. Composition
>>>> is
>>>> started by z, the process continues with lmnop, etc. How does
>>>> ContainerController, BaseCompose FlowComposer, etc. all interact with
>>>> each other.)
>>>> 
>>>> It's really hard to work on a framework, when the details on its
>>>> architecture is really sketchyŠ
>>>> 
>>>> On Apr 6, 2014, at 2:01 PM, Maurice Amsellem wrote:
>>>> 
>>>>> This one maybe ?
>>>>> 
>>>>> 
>>>>> http://help.adobe.com/en_US/as3/dev/WSb2ba3b1aad8a27b0-1b8898a412218ad3
>>>>> df
>>>>> 9-8000.html
>>>>> 
>>>>> 
>>>>> -----Message d'origine-----
>>>>> De : Harbs [mailto:harbs.li...@gmail.com]
>>>>> Envoyé : dimanche 6 avril 2014 12:55
>>>>> À : dev
>>>>> Objet : Docs on TLF composition?
>>>>> 
>>>>> While working on TLF, I constantly forget the finer points of the
>>>>> composition flow. It's highly inefficient to constantly step through
>>>>> the
>>>>> code to figure out exactly what happens when and by what.
>>>>> 
>>>>> I'm thinking of putting together a doc which specifies the flow and
>>>>> how
>>>>> all the classes work together. Before I do this, I'm wondering if
>>>>> anyone
>>>>> knows of any documentation explaining the architecture.
>>>>> 
>>>>> Harbs
>>>> 
>>> 
>> 
> 

Reply via email to