Keyboard - additional methods for the keyboard

text_focus (1).aia (12.5 KB)

Does it make sense to use helper blocks for the button actions since every AppInventor distribution supports them now?

Does Kodular also use helper blocks? The extension is old, when I made it Kodular didn't use helper blocks so I didn't add them.

Yes it does, in the newer versions.

Updated, added method (KeyboardChangeScreen) that allows keyboard to be displayed over components without moving them.

1 Like

I used an extension to fix a problem that the blocks in mit cannot do which is that everytime the keyboard pops ups, the screen background shrinks. I tested it in companion mode and it works, but when I made it into an apk and installed it on my phone, the problem occurred again which means the extension did not work. What causes this?

Which extension are you talking about?
Please provide a link to the extension and a screenshot of your relevant blocks

Which problem? Please elaborate, see also

Taifun

this is the normal screen

this is the problem when keyboard pops up

I now moved your question into its correct thread
Also I removed the extension from your post, because only extension authors are allowed to upload their extensions
Taifun

Put your aia project here so I can test it.

But before you do that, place the "Keyboard Change Screen" block in the Initialize blocks of the screen. It is called once, and calling it in GotFocus may be too late...

Sorry for the wrong posting, I am new here
Anyways, You are definitely right the got focus was too late, I put the keyboard change screen on the screen initialize and it perfectly works now.
THANK YOU VERY MUCH..

1 Like

@Patryk_F

Can you please add support for PasswordTextBox component?

With this extension you can make a PaswordTexBox from a regular TextBox.

Unfortunately, this extension conflicts with the TaifunTools extension.
And it also conflicts with the com.sunny.SystemUI.aix extension.
:disappointed:

1 Like

Can you please elaborate? What exactly is the conflict? What happens, if you use both extensions in the same project? Any example?

Taifun

I think he's just testing it on the official Companion, which doesn't work with many extensions.

1 Like

Exactly. The conflict is only in Companion, the builded app works.
Can I use any other Companion?

You might try with the bugfix companion app 2.73t6:

If asked, select "Not Now"

Thanks TIMAI2!
Both extensions work together in the companion version 2.73t6.

And thanks to Patryk_F for the useful extension.

1 Like