I just committed a fix to this. It’s slightly concerning to me that the fix was in the Operation, but this case should be resolved.
Basically, it seems that the preserved terminator span is different in the new TLF code than it was in the old code, so a reference was becoming invalid. I’ll keep my eyes out for other cases where this might become an issue. I’m running the Unit Tests right now. I’ll see what comes up… Harbs On Dec 19, 2014, at 12:41 AM, Harbs <harbs.li...@gmail.com> wrote: > Thanks for the observations. I’ll look more tomorrow. > > The real question is what changed that’s causing this error. Changing > something that I have not touched in TLF is not the right way to fix this > IMO. I need to figure out what I broke and address the source of the problem > before I try to work around this RTE. > > On Dec 19, 2014, at 12:18 AM, piotrz <piotrzarzyck...@gmail.com> wrote: > >> Harbs, >> >> After debugging I see something like this: >> >> http://images.devs-on.net/Image/jg5EXavR0Yo3N065-Obszar.png >> >> We are doing undo on _memento, but it doesn't have our deleted text in the >> MementoList, because our text is inside delSelOp.undo(). >> >> Doing _memento.undo() we are getting these error, but probably if we do undo >> on delSelOp we will have correct data. >> >> Just my findings after long debugging :) >> >> Piotr >> >> >> >> ----- >> Apache Flex PMC >> piotrzarzyck...@gmail.com >> -- >> View this message in context: >> http://apache-flex-development.2333347.n4.nabble.com/DISCUSS-Release-Apache-Flex-4-14-0-tp43390p43757.html >> Sent from the Apache Flex Development mailing list archive at Nabble.com. >
