In ContainerController, updateVisibleRectangle() adds a scrollRect. You can
access hasScrollRect to see if a scrollRect is added to the container
without accessing the DisplayObject.scrollRect property, which can have
side effects in some cases. According to the comments, "Accessing
scrollRect when null changes the rendering behavior of flash player." I'm
not sure what those side effects are. You might want to check that both the
vertical and horizontalScrollPolicy is set to off which appears to prevent
the container.scrollRect property being set.
There is one other thing I noted in the comments,
// If scrolling is turned off, and flow is vertical, then we
need to adjust the positions of all the lines. With
// scrolling turned on, we don't need to do this because the
adjustment is done in the Player when the scrollRect
// is set up correctly. But with the scrollRect, we also get
clipping, and if scrolling is turned off we want to
// have the clipping turned off as well. So in this case we do
the adjustment manually so the scrollRect can be null.
// NOTE: similar adjustments are made in TextContainerManager
On Tue, Apr 8, 2014 at 1:17 AM, Harbs <harbs.li...@gmail.com> wrote:
> The content is clipped even if you use a Sprite as a container.
>
> I used the second example here:
> http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flashx/textLayout/container/ContainerController.html
>
> The text in the second container was clipped at the bottom until I
> scrolled up.
>
> On Apr 7, 2014, at 10:29 PM, Alex Harui wrote:
>
> > AFAIK, TLF does not support scrolling. The container does. For Flex
> > TextArea, the RichEditableText is clipped by a scrollRect.
> >
> > If you are seeing ascender/descender clipping that might be caused by
> > improperly sizing the TextLine or a rendering issue in the player.
> >
> > -Alex
> >
> > On 4/7/14 10:00 AM, "Harbs" <harbs.li...@gmail.com> wrote:
> >
> >> 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-1b8898a412218a
> >>>>>>> d3
> >>>>>>> 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
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> >
>
>
