Bug from 2014 - still causing problems

[Iphonelagi]

hi Jacque

Yes, In the end Todd bit the bullet and did it with the native field on both iOS and Android ... now for the testing and inevitable quirks.

this  lesson gave initial food for thought

http://lessons.livecode.com/m/4069/l/29112-how-do-i-use-native-text-controls-on-mobile

But  a newbie learning LC will look at it as broken, and the idea is to make the learning curve easier. The other thing Is others will get  bitten in the bum when you leat expect it. We tested both on IOS and android but never used delete on adroid for over a year ... I suppose cos you don’t expect that to fail.

Still there is no excuse for not fixing something for 5 years  that doesn’t even need a recipe.

The bug which Klaus commented on will frustrate even more people when they try to get their buttons looking how they want and finding the settings don’t work as they should.

<here endeth the sermon>

Lagi


Sent from my iPhone

> On 25 Oct 2019, at 19:35, J. Landman Gay via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> On 10/25/19 11:44 AM, Lagi Pittas via use-livecode wrote:
>> 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"?
> 
> I use native fields almost all the time. If you write a generic handler that calls mobileControlCreate and sets some basic properties, it's a one-liner.
> 
> I have seen the LC field problems on Android but they were much worse in earlier versions. They seem a little better now, but to be safe I use native fields anyway.
> 
> -- 
> Jacqueline Landman Gay         |     jacque at hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
> 
> _______________________________________________
> 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