Skip to main content
Known Participant
November 16, 2010
Question

TLF 2.0 build 200 with flex sdk hero

  • November 16, 2010
  • 1 reply
  • 1525 views

Hello Guys,

I needed the last release of the TLF that has couple of bugs that I encounter fixed.

I dropped textLayout instead the one that is in hero.

It works until the moment I use editable controls then it says:

ReferenceError: Error #1056: Cannot create property flashx.textLayout.edit:IEditManager::delayedOperations on flashx.textLayout.edit.EditManager.

at spark.components.supportClasses::RichEditableTextContainerManager/createEditManager()

at flashx.textLayout.container::TextContainerManager/invalidateInteractionManager()

at flashx.textLayout.container::TextContainerManager/http://ns.adobe.com/textLayout/internal/2008::convertToTextFlowWithComposer()

at flashx.textLayout.container::TextContainerManager/mouseDownHandler()

at spark.components.supportClasses::RichEditableTextContainerManager/mouseDownHandler()

at flash.events::EventDispatcher/dispatchEventFunction()

at flash.events::EventDispatcher/dispatchEvent()

at mx.core::UIComponent/dispatchEvent()

at mx.managers::SystemManager/mouseEventHandler()

What can it be?

This topic has been closed for replies.

1 reply

Adobe Employee
November 16, 2010

We don't post the Flex builds, so I'm afraid I don't know when they will post a new build, although I will certainly inquire and see if they have a date for that. One thing you could try is to take the Flex source, and make the API change yourself, and then rebuild Flex.

The problem you are running into is that there is a TLF API that was used in Flex that was renamed in TLF. The new TLF (build 200) is using the new name, while the older version of Flex is using the old name. API changes are all listed in the release notes (and in the checkin notes), the one that is hitting you is this one:

   * API Change: Renamed IEditManager.delayedOperations to allowDelayedOperations. Renamed IEditManager.delayedUpdate to delayUpdates.

We apologize for the inconvenience -- we go through an API review process before finalizing an API to make sure that naming and functionality is as clear and simple as we can make it, but it does mean that you can get caught in the middle by changes caused by the review. Overall, I do think it improves the API, but it is painful when it hits you.

If you make the corresponding change to Flex, that should fix this problem.

- robin

Participating Frequently
November 17, 2010

Hi There - We post updated builds of Flex SDK "Hero" here: http://opensource.adobe.com/wiki/display/flexsdk/Download+Flex+Hero

However, these are "special" builds which do not contain the new in-development Flash Player & AIR runtimes nor the new mobile features being added to the Flex framework. However, they will contain new TLF builds so you can keep an eye on that page to grab a new TLF swc.

HTH,

deepa

tork314Author
Known Participant
November 17, 2010

Hello Deepa,

I think it is a different problems we discuss in here.

TLF guys are changing/renaming SDK.

they post new TLF, but there is no corresponding SDK.

Can you, please, return to posting nightly builds?