Return-Path: X-Original-To: apmail-flex-issues-archive@minotaur.apache.org Delivered-To: apmail-flex-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 849111092B for ; Wed, 18 Sep 2013 15:42:25 +0000 (UTC) Received: (qmail 83566 invoked by uid 500); 18 Sep 2013 15:42:08 -0000 Delivered-To: apmail-flex-issues-archive@flex.apache.org Received: (qmail 83086 invoked by uid 500); 18 Sep 2013 15:41:54 -0000 Mailing-List: contact issues-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list issues@flex.apache.org Received: (qmail 83059 invoked by uid 99); 18 Sep 2013 15:41:51 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Sep 2013 15:41:51 +0000 Date: Wed, 18 Sep 2013 15:41:51 +0000 (UTC) From: "Alex Harui (JIRA)" To: issues@flex.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FLEX-33409) TLF crashes when hypens are shown in a multi span textFlow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLEX-33409?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1377= 0891#comment-13770891 ]=20 Alex Harui commented on FLEX-33409: ----------------------------------- Well, you can run the profiler to see what is going on, but I'm pretty sure= the problem is that, in order to workaround this player bug, we have to re= -render every line in the textflow starting from the first one that has a h= yphen. Fundamentally, there is a player bug and I am just trying to workar= ound it. You can try some test cases of an equivalently large TextFlow without any h= yphens in it and see if performance is better, and also try without hyphens= with the ContainerController flag set to false and see if the old code pat= hs perform better. You can try bugging the FlashPlayer team to fix the bugs I filed in their n= ext release. I think the next level of a workaround is to virtualize the t= extflow and I'd rather not spend the time on it unless I see lots more peop= le running into this problem. I'm happy to try to answer questions if you = want to try it yourself. Basically, the assumption is that a VERY large te= xtflow doesn't fit on the screen so you'd have to virtualize by only trying= to render a subset of the original TextFlow starting with the first visibl= e line. -Alex=20 =20 > TLF crashes when hypens are shown in a multi span textFlow > ---------------------------------------------------------- > > Key: FLEX-33409 > URL: https://issues.apache.org/jira/browse/FLEX-33409 > Project: Apache Flex > Issue Type: Bug > Affects Versions: Adobe Flex SDK 4.6 (Release) > Environment: TLF editing > Reporter: Woodwing Developer > Assignee: Alex Harui > Priority: Blocker > Labels: TLF, crash, editing, hyphen, span, textflow > Attachments: BaseCompose.as, ComposeState.as, ContainerController= .as, ExampleDebug.fxp, FLEX33409.patch, FlowComposerBase.as, FlowLeafElemen= t.as, ParagraphElement.as, Test.fxp, textLayout.swc > > > When soft hyphens are used and shown, in a textFlow with 2 or more spans,= TLF crashes when typing. > Import the underlying text flow xml. Resize the text area until the hyphe= n is visible. Then start typing AFTER the hypened word, also pressing the e= nter key. TLF crashes. > Sample textFLow (if the soft hyphen is not show, insert a new one in the = appropriate word): > >

> Firs= t Span > Second s= pan. This text has a hypen in the next long word LongWord=C2=ADWithAHyphen.= Make sure the hypen is shown! Then start typing and pressing enter till TL= F crashes (should happen fast enough) >

>
> It seems that the textLine is damaged but the text engine fails to recomp= ose the line properly. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrato= rs For more information on JIRA, see: http://www.atlassian.com/software/jira