I’m experiencing an issue with native text fields on iOS (both on device and in the xcode simulator)
When a user manually adjusts the cursor position in an input field and continues to input text via the keyboard, the last character inserted is being appended to the end of the .text value string. If they continue to type, the characters move to their correct position, all except for the last inserted character.
The native text field displays what is typed correctly, it is only the text field’s .text value that is incorrect.
Hi, we have this bug too, as well as some facebook issues - 1260.
Can someone confirm that you will continue to fix regression bugs in the legacy builds? There will be a 1261 that fixes Facebook login and the text input thingy, no?
I can confirm this as well, it’s been a pretty big annoyance for my users to have to enter their text multiple times. Especially since my app is largely text-based.
This has been fixed in a recent G2.0 build (I can look up which build number if necessary). We will also look into getting that into a 1.0-based build if possible.
@mail1347, just as a side note, myself and several other developers have found that converting to G2.0 is easier that expected, even without relying on V1 Compatibility Mode (which should make it even easier). Last night, I ported 90% of a fairly complex app over to 2.0 functionality within about 4 hours, and I could cut that time in half now that I’m familiar with the process. The migration guide can help toward this goal, if you wish to do so.
Hi, we have this bug too, as well as some facebook issues - 1260.
Can someone confirm that you will continue to fix regression bugs in the legacy builds? There will be a 1261 that fixes Facebook login and the text input thingy, no?
I can confirm this as well, it’s been a pretty big annoyance for my users to have to enter their text multiple times. Especially since my app is largely text-based.
This has been fixed in a recent G2.0 build (I can look up which build number if necessary). We will also look into getting that into a 1.0-based build if possible.
@mail1347, just as a side note, myself and several other developers have found that converting to G2.0 is easier that expected, even without relying on V1 Compatibility Mode (which should make it even easier). Last night, I ported 90% of a fairly complex app over to 2.0 functionality within about 4 hours, and I could cut that time in half now that I’m familiar with the process. The migration guide can help toward this goal, if you wish to do so.
Sorry, Brent, but I disagree. If there are third-party libraries with buggy unsupported code it can be a nightmare. We have one project that uses LoqSprite (now 2 weeks into upgrading) and another one that uses Lime (even more horrendous, we canceled doing the upgrade). Not only is upgrading painful, I now have to maintain a virtual PC with an old Corona version just to maintain the Lime-based project, while working on the other.
I’ve never seen a framework by any vendor (Android, iOS, Java, .NET, Unity, XNA, OpenGL, DirectX to name a few I’ve used) that actually breaks existing APIs. Quite the opposite, they drag the same old legacy functions for decades. And now you simply decide to break every single Corona project that has been written? Nice going, guys
Edit: OK, I lied. Apple broke our builds with iOS 7 recently. And now Corona does the same. Prepare to be sued for patent infrindgement
Sorry, Brent, but I disagree. If there are third-party libraries with buggy unsupported code it can be a nightmare. We have one project that uses LoqSprite (now 2 weeks into upgrading) and another one that uses Lime (even more horrendous, we canceled doing the upgrade). Not only is upgrading painful, I now have to maintain a virtual PC with an old Corona version just to maintain the Lime-based project, while working on the other.
I’ve never seen a framework by any vendor (Android, iOS, Java, .NET, Unity, XNA, OpenGL, DirectX to name a few I’ve used) that actually breaks existing APIs. Quite the opposite, they drag the same old legacy functions for decades. And now you simply decide to break every single Corona project that has been written? Nice going, guys
Edit: OK, I lied. Apple broke our builds with iOS 7 recently. And now Corona does the same. Prepare to be sued for patent infrindgement
This problem is bad. In build 1259, not only does it update the end of the text instead of the middle, but it also considers a select/cut action to be the deletion of the last character of the text. User selects and cuts characters 3-8 of the text, and character 12 disappears instead.
It also seems like autocomplete doesn’t work anymore.
As far as migration to G2 being “easy”, I use a lot of widgets. Widgets have their centers as origin in G2 instead of top left. Center origin causes fuzzy text, as we know from many other posts/discussions (fractional x/y values cause fuzziness due to aliasing, and the solution is to use non-center origins to avoid fractional x/y values for left and right edges of text objects).
So, I don’t see G2 as an easy solution. I see retrofitting the G2 fix for a bad bug into a Corona G1 build as an easy solution, or a having the compatibility mode include all the G2 fixes and not have widget incompatibilities as an easy solution.
