Skip to main content
J
JoshuaMostafa
Participating Frequently
July 29, 2010
Question

Column heights wrong when text is scrolled

  • July 29, 2010
  • 1 reply
  • 816 views

Hi there,

I've found a problem with TLF - searched the forums and can't find any mention of it on the forums or elsewhere.

What happens is that if I have a container with more than one column, and vertical scrolling allowed, as soon as there is enough text to require scrolling, only the right-most column scrolls. The other columns will contain only enough text to reach the height of the container.

Example here - just type or paste in enough text to make it scroll:

http://lab.almirun.com/as3/ColumnScrollTest/ColumnScrollTest.html

Example source here:

http://lab.almirun.com/as3/ColumnScrollTest/srcview/index.html

Version number is 1.1 and build number is 602 (746231).

Cheers

Josh

This topic has been closed for replies.

1 reply

R
Adobe Employee
rdermer
Adobe Employee
July 29, 2010

TLF doesn't support column balancing which would spread the lines evenly among the columns.  It's a possible feature for 2.0.

Richard

J
JoshuaMostafaAuthor
Participating Frequently
July 29, 2010

It's not that I want the text to be spread evenly - I just want the height of the actual controller to be respected by the columns when the text increases to the point where the container scrolls. This is a bug, not a missing feature!

R
Adobe Employee
robin_briggs
Adobe Employee
August 2, 2010

I'm not sure what you're expecting. If you turn off the scrolling, then the text will fit the container's compositionHeight, and any text that doesn't fit is pushed into the next container if there is one. With the scrolling on, the compositionHeight dictates how much of the text is visible, but you can scroll to text that falls past the compositionHeight.

If scrolling is turned on, and there is enough text to scroll, TLF composes only up to the part that is visible by default. In this circumstance, when you get the contentHeight, it will return an estimated value. If you want the correct value, compose the text first (call composePosition), and then ask for the contentHeight. It is set up this way so that clients have control over whether TLF takes the time to do a full recompose or not. On a long text flow this can make a big difference.

Can you be more specific about the bug you are seeing?

Thanks,

- robin

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices