I have a list with textInput in a mobile project. When i scroll the list the value of textInput is "flying". Look the image, this happen in the simulator and in the device.
In this image the number "two" is the number of "18 - Sony Vaio".
I create the textInput overrides createChildren function on the IconItemRenderer:
override protected function createChildren():void
var txtQtd:TextInput = new TextInput();
txtQtd.id = "txtQtd";
txtQtd.width = 70;
txtQtd.height = 40;
txtQtd.x = this.parent.width-90;
txtQtd.y = 25;
txtQtd.maxChars = 4;
txtQtd.softKeyboardType = SoftKeyboardType.NUMBER;
This is one of the many, many bugs that the new StateText skin for the TextInput and TextArea from the Flex 4.6 introduced.
You can do this skinClass="spark.skins.mobile.TextInputSkin" as many users recomended but with get new problems like the skin lose the default rounded corners (became the default skin from flex 4.5 instead of 4.5.1) and you will get other bugs.
There is one solutuion to use the Flex 4.6 but the stability of the TextInput and TextArea from the Flex 4.5.1 that is the original source code of the TextInputSkin and TextAreaSkin of the Flex 4.5.1. This is already speaked in the forum.
Thank all of you for the aswers...
I cant use skinClass="spark.skins.mobile.TextInputSkin" because i will lose softKeyboardType and this is very important to the application.
Let's in the future if that bug will be fixed.
In my case I have a costum text input, preventing the keypad that popups a callout with a calendar (for dates), the same for time, numbers and integers and use the keyboard only for free text (strings) so I will never need the new features from the stage text.
In your case if you realy need the new features from the StageText you will need to wait the fix but I will not expecting soon a new release (now only on apache).
IMHO it's the best choice because you now longer are depent on OS or have issues and different systems (worst and update that causes a bug and that appens to me in PlayBook with stagetext ).
Best have something generic.
You can see the result in my app :
For iOS, I dont have a demo version to demonstrate because they refuse demo or lite versions
You can put the following CSS in your main stylesheet to fix it for all TextInputs in your application:
/* Fix for floating text of inputs while scrolling */
Maybe create a component which has an invisible StageText TextInput and a visible one with the TextInputSkin. Then the visible one shows the value entered by the invisible which requests softkeyboard and passed the value in changeHandler onto the visible one ?
Use the old Flex 4.5 mobile skin as mention.
Btw: See the look and fill of my last major release : https://play.google.com/store/apps/details?id=air.com.softbycloud.pers onalfinances
Currently with Apache Flex 4.9.0 maybe this was fixed.
There's bug filed over here please have a look and vote if you are facing the issue
We might have a solution to this, http://blog.flexicious.com/post/Scrolling-Issues-With-TextInput-for-Fl ex-Air-Mobile-Native-StageText.aspx - seems to work for our scenarios.