GUI-O Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    TI keyboard covers my input

    Scheduled Pinned Locked Moved
    Report Bugs
    3
    15
    210
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      RudiP
      last edited by

      @kl3m3n said in TI keyboard covers my input:

      The canvas should be automatically pushed up when you focus on the input widget, like I've shown in the animated image

      When I tap the Text Input widget, the keyboard appears, but the widget is still hidden under the keyboard. The text input widget only showed up once after more than 20 attempts, and that after several seconds!

      K 1 Reply Last reply Reply Quote 0
      • K
        kl3m3n @RudiP
        last edited by

        @RudiP Hi!

        Can you please share which device you are using and Android version?

        If I understand correctly, this worek for you before? And now it stopped working? Was this on the same device?

        Thanks!

        Kl3m3n

        1 Reply Last reply Reply Quote 0
        • R
          RudiP
          last edited by

          The device is Samsung A55, Android version 16. In all attempts > 100, the TI widget showed up only once.
          Could it be an error in the TI declaration?

          BT.print("|TI UID:ti_SMS3 X:70 Y:68 W:60 BGC:#F5F5F5 FGC:#212121 SHC:#FFC107 TXT:"" LALP:0 SCI:2\r\n");

          K 2 Replies Last reply Reply Quote 0
          • K
            kl3m3n @RudiP
            last edited by

            @RudiP Hi!

            No, your initialization is not the problem.

            I will try to find out the cause why the canvas is not being pushed up. First, I need to reproduce the error.

            I will let you know about further developments.
            Thanks for your patience.

            Best regards,
            Kl3m3n

            G 1 Reply Last reply Reply Quote 0
            • G
              gammda @kl3m3n
              last edited by

              @kl3m3n
              I have found the same in some cases. Maybe it is something in the phone's display settings.

              1 Reply Last reply Reply Quote 0
              • K
                kl3m3n @RudiP
                last edited by kl3m3n

                @RudiP I could not reproduce the problem, but there was a potential issue that could cause this behaviour.
                Please try v1.0.111. I have tested this version on multiple devices, including Samsung.

                Best regards,
                Kl3m3n

                1 Reply Last reply Reply Quote 0
                • R
                  RudiP
                  last edited by

                  I upgraded GUI-O to v-1.0.111 . As for my problem, nothing has changed. The keyboard still covers the TI or NI input field.

                  R 1 Reply Last reply Reply Quote 0
                  • R
                    RudiP @RudiP
                    last edited by

                    The screen of my old A71 phone works, the screen is pushed up. The latest version of GUI-O is installed on the a71.

                    R 1 Reply Last reply Reply Quote 0
                    • R
                      RudiP @RudiP
                      last edited by

                      What phone or GUI-O settings could be causing the widget not to rise above the keyboard?

                      K 1 Reply Last reply Reply Quote 0
                      • K
                        kl3m3n @RudiP
                        last edited by

                        @RudiP Hi.

                        I am fairly positive that settings are not the cause of this.

                        Can you first try changing the keyboard? I assume that your default keyboard is Samsung keyboard. Try changing it to Gboard (should be something like Android settings -> Additional settings -> Language and input).

                        Best regards,
                        Kl3m3n

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post