Linked continer issue

Question

Hi Guys,
This issue is specific to TLF 1.1 and does not happen in TLF 1.0.
Have 2 linked container and try typing on the second para of second container, you will see a flicker . Also if you hit "ENTER" in the first para of second container the content will dissapear .
You can try the same here ..
Is this a bug in TLF or am i doing something wrong ?
Thanks
Rafique Gilani

Answer 1

I've been looking into this -- thanks for reporting this! I have a workaround for you to try. I haven't done extensive testing with it, but it fixes the basic problem. The bug is caused by the new incremental composition. We added new code for composing from the middle of the container, instead of requiring to start at the beginning each time. This bug happens when we are applying the incremental composition logical, but are starting from the start of the second or subsequent container. In this case, it gets confused about where the composed lines should go. The fix is to extend the damaged area slightly, to include the very end of the previous container. You can do this by adding an event listener for DamageEvent to the TextFlow. When you get a damage event, and the damaged area starts at the start of the controller (and its not the first), damage backward by one character.
Here's an example event listener:
        private function damageHandler(event:DamageEvent):void
            if (event.textFlow == activeFlow)
                var controllerIndex:int = activeFlow.flowComposer.findControllerIndexAtPosition(event.damageAbsoluteStart);
                if (controllerIndex > 0)
                    var controller:ContainerController = activeFlow.flowComposer.getControllerAt(controllerIndex);
                    if (controller.absoluteStart == activeFlow.flowComposer.damageAbsoluteStart)
                        activeFlow.tlf_internal::damage(controller.absoluteStart - 1, 1, false);
You can attach this event listener to textflow as follows:
            activeFlow.addEventListener(DamageEvent.DAMAGE, damageHandler, false,0,true);
Let me know how this works -- my apologies for the bug.
Thanks,
- robin