Bug from 2014 - still causing problems

[Brian Milby]

Probably a big advantage to using native fields on mobile is cut/copy/paste.

Thanks,
Brian
On Oct 25, 2019, 12:46 PM -0400, Lagi Pittas via use-livecode <use-livecode at lists.runrev.com>, wrote:
> We are working on an App that runs on IOS/Android and Windows so making
> sure
> the Codebase and elements/objects are as much the same on each platform is
> important.
>
> Even more important is that we use the same elements on all platforms
> including LC fields that are much easier to use than native text fields.
>
> We are close to launching, and a couple of weeks ago noticed that the
> delete/backspace key on Android
> has a mind of its own - Not deleting, sometimes adding a space or a
> duplicate character , then deleting.
>
> We had to code for a native field on Android but not only does it look
> uglier out of the box we can't use the code for our "placeholder" routine.
> and other properties and the logic for navigation and validation without a
> lot of modification.
>
> Because of the way the App works just straight overlaying code does not
> work without a lot of wasted energy and extra testing.
> In the end we have decided to use native fields on both Android and IOS
> to save having different code on 3 platforms.
> We will focus on the LC field and then have a behaviour that then overlays
> the native field above but uses the properties already set on the LC field.
> - but it is a good few days of extra work and testing.
>
> This bug in Android has been there since 2014
>
> https://quality.livecode.com/show_bug.cgi?id=13229
> https://quality.livecode.com/show_bug.cgi?id=18876
>
> http://forums.livecode.com/viewtopic.php?t=28699
>
> The sentiments here are the same as what Klaus posted in the forums this
> morning and in Bugzilla ....
>
> https://quality.livecode.com/show_bug.cgi?id=11902
>
> Is there any point adding comments to the current buglzilla or is it the
> case that if no one has added a comment for 2 years it can't be a problem?
> In fact the bug Klaus mentioned was one I came up against when I first
> started using Livecode , and thought it was my lack of understanding so
> never even bothered mentioning it in the forum.
> Turns out I was wrong.
>
> Any idea if this has been fixed and we don't know about it or there is a
> very easy workaround. Still posting even though we are coding around it but
> this has to be fixed
> because anybody who buys Livecode for Android development will hit this
> particular "feature"
>
> <LIGHT COMES ON>
> Jacque, you do a lot of Android programming if memory serves - do you use
> native all the time for text input
> or are we just "holding it wrong"?
>
>
> Lagi & Todd
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode