My solution for this issue is: Write your own Class named VisualStageText which extends the SpriteVisualElement Class and implements the IEditableText interface, and two properties have to be declared:
1. stageText:StageText, which is used for renderering the actual text. 2. target:IVisualElement, which is used for listenning position changes during scrolling, usually you should pass the container object which contains the VisualStageText instance, it may not be the direct parent of the VisualStageText instance, more likely it would be the parent.parent.parent.... of the VisualStageText instance, which is a direct child of the Scroller instance. I only listed two core properties above, of course you have to declare many other properties by yourself and implement the IEditableText interface. The idea is to listen to the target's MoveEvent.MOVE, Event.RENDER ... events, when these events occur, update the stageText.viewPort property based on the VisualStageText instance's x, y, width, height, and the target's x, y, width, height, well I think you get the point. Write your own TextInputSkin, bind VisualStageText mxml tag as your textDisplay:IEditableText skin part, like: <texts:VisualStageText id="textDisplay" with="100%"/> Then you have to assign the correct container to the VisualStageText's target property, well I think you can figure it out yourself. Good luck! DarkStone 2013-09-30 At 2013-09-30 10:28:56,"Flexicious.com" <flexici...@gmail.com> wrote: >This may not be a Flex/Apache issue, but just wanted to see if anyone has >been successful with text on Air mobile. > >The issue basically revolves around the native text input. It is rendered >on top of the display list, and it does not scroll within its parent >scroller. So dropdowns and such that render on top of it do not hide it, >and if the user scrolls the text stay in place. There are some more >details here: > >http://stackoverflow.com/questions/15840504/what-options-are-available-for-handling-text-input-on-android-using-adobe-air >https://bugbase.adobe.com/index.cfm?event=bug&id=3302441 > >Some have suggested using the older spark.mobile.TextInputSkin but with >Air 3.8 and iOS7 on iPad , the workaround suggested is not an option. It >seems to be even more problematic, as you type it selects what you have >typed so you cannot effectively type anything without erasing what was >there. > >A comment from an Adobe person here suggests the issue with the older >TextinpustSkin is a Flex SDK issue. >https://bugbase.adobe.com/index.cfm?event=bug&id=3292370 > >Has anyone run into this, if so, been able to handle it gracefully?
