composeuisuite / ohteepee Goto Github PK

The library exhibits a delay in character rendering during rapid typing, occasionally resulting in skipped characters. This behavior impacts user experience, particularly during fast-paced input sessions.

Let's say I have the following code

    var otpValue: String by remember { mutableStateOf("1234") }
    
     OhTeePeeInput(
         value = otpValue,
         autoFocusByDefault = true
      ....
    )

OTP value is being populated using GMS service to read SMS from device.
Initial value would be Empty but the latest value could be 1234 provided automatically.
In this case, the focus should be

1. Either removed. Active cell should be disabled.
2. Moved to the last cell.

Great library.

Is it possible to start from right to left?

I'm currently migrating views from xml to Jetpack Compose.

The pin entry view style I used with xml was similar to Material Design Filled text field. With a colored border below the active cell.

Is there a way to achieve something similar with this library?

Focus should only be the next editable field.

User shouldn't be able to tap any random field to start editing OTP. (Unless the cell is already populated I guess)

Hello and thank you for your fascinating library. Below, I would like to address some of the bugs I noticed within the library.

For the first time, the keyboard opens automatically, but after closing, it does not reopen by clicking on the OTP. There is an issue with focusing on the OTP.

The text that is written is no longer removable and editing it encounters problems. There is no control over the imeAction keyboard, and its type cannot be changed.

It is better that any character clicked on a cell is editable.

i am unable to enter the text field values in sumsang device but it's working fine in pixel device. your sample project is working fine but any implementation as a library getting stuck in 2nd field. Kindly sync your project or update library code

Hi, I'm dealing with an issue where, when I switch focus from one tile to another, my view jumps. This is probably related to the fact that the keyboard raises the content higher.

Hi,
in the handleCellInputChange we have something like this:
val formattedNewValue = newValue.replace(placeHolder, String.EMPTY) .replace(obscureText, String.EMPTY)

Is the method for replace placeholder really needed? Currently in my project i need to have placeholder set as "0", but i need to allow user to type "0" in the cell. This function blocks user for typing "0" because this input char is removed