Getting Contents Of A Native Android Field Widget

[Googie85]

Hi Guys!!

I am having problems with the following code:

Code: Select all

on keyDown theKey 
   put the text of widget "ONE" into blah
   put the number of chars in blah into blah
   answer blah
end keyDown

The above code is under the "ONE" widget. What am I doing wrong??

Many Thanks,

Googie.

[richmond62]

Dunno; this worked:

Code: Select all

on keyDown KKK
   put the text of widget "ANF" into XYZ
   put the number of chars in XYZ into ABC
   answer ABC
end keyDown

Possibly using blah all the time.

[Googie85]

Thanks for your reply, it didn't work.

Anyone have any more ideas??

Many Thanks,

Googie.

[richmond62]

It worked on MacOS.

[Googie85]

Thanks for your help!!!!

I am using an Android Native Field. Maybe it might not work on macOS...

Thanks, Richmond!!!!

[Klaus]

Maybe KEYDOWN etc. do not work with Android native fields?
Unfortunately the Dictionary gives no hint.

Try the script with an "ordinary" LC text field and see if that works.
If yes, then it does not work this way with a native field.

[Googie85]

Thanks Klause!!

I was hoping to use the Native Field to disable the Auto Correct in the field. I will keep looking for a solution...

Thanks,

Googie.

[Klaus]

KLAUS, my name is KLAUS, no E at the end!

[Googie85]

Loser... Why be rude...

[Klaus]

Mimimi?

Emphasizing something with capital letters is not being rude!
And thank you for the "loser", much appreciated!

[richmond62]

I tried my code with an Android native field widget
on MacOS.

What becomes clear is that development on a
desktop machine for Android is beset with
lots of traps.

Oh, Googie, as an expert at offending people,
using words like 'loser' round here will only
make you lose, no one else. So, please stop
doing that.

[jacque]

KeyDown isn't supported in the native Android field. Use "on textChanged" instead.

You can see all the supported commands and functions in the dictionary if you look up "Android native field".

[jacque]

I tried my code with an Android native field widget
on MacOS.

What becomes clear is that development on a
desktop machine for Android is beset with
lots of traps.

Native controls don't work well unless you're in the OS that supports them. You can't test an Android or iOS widget on a computer. There aren't any traps per se, just differences among operating systems.

[richmond62]

Native controls don't work well unless you're in the OS that supports them.

Thank you very much for explaining that explicitly.

[jacque]

I suppose the only "trap" is the generic one where you have to indulge in the behavioral loop that requires a code change, a recompile, a test, repeat, over and over until you get it right. It's tedious when writing for mobile but I don't see any way around it. The instructions the engine requires are only available on the supported OS.