[ 
https://issues.apache.org/jira/browse/FLEX-34247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004760#comment-14004760
 ] 

Alex Harui commented on FLEX-34247:
-----------------------------------

If you have a simple test case that shows the difference, please attach it. My 
test app is just:

<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"; 
                           xmlns:s="library://ns.adobe.com/flex/spark" 
                           xmlns:mx="library://ns.adobe.com/flex/mx" 
minWidth="955" minHeight="600">
        <fx:Declarations>
                <!-- Place non-visual elements (e.g., services, value objects) 
here -->
        </fx:Declarations>
        <s:TextArea width="100%" height="100%"/>
</s:Application>


> Performance with TextArea using TLF 
> ------------------------------------
>
>                 Key: FLEX-34247
>                 URL: https://issues.apache.org/jira/browse/FLEX-34247
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: TextArea
>    Affects Versions: Apache Flex 4.12.0
>         Environment: Win 7 64 Bit, FP 13
>            Reporter: Benjamin Ludwig
>              Labels: regression
>         Attachments: log4.txt
>
>
> I run into performance issues with TextArea with Apache Flex 4.12.
> After pasting a text of approx. 400000 chars into TextArea, it freezes for 
> some time but becomes responsive again. Then I noticed the follwing:
> In Flex 4.6: I can enter chars into TextArea at any speed without any 
> problems.
> In 4.12: the FlashPlayer freezes on each char entered for some time, 
> rendering TextArea for long texts unsable. 
> I know there is much effort in TLF, but this feels like a downgrade, because 
> handling huge texts in a very fast way was my reason to choose TLF, but this 
> was about 2 years ago.
> Do I now have to stay on tlf 1.0 for handling huge texts? Would be sad :(
> regards
> benny



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to