Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ShouldSecureText Works on the new characters typed but not on the old one. #75

Open
Chokaaaa opened this issue Aug 30, 2022 · 0 comments

Comments

@Chokaaaa
Copy link

shouldSecureText = true works only on new characters entered but it still hides for the old characters ended.

so if I am entered 2/4 numbers and got 2 of them ** (secured) and make a shouldSecureText = false the previous ** are not being affected I either need to refreshView but it deletes the all entries cause its calling a clearPin() could you please fix that? so the entered text no matter when I press it, its updates the current characters that are already exists?

@Chokaaaa Chokaaaa changed the title ShouldSecureText Works on the new characters ended but not on the old one. ShouldSecureText Works on the new characters typed but not on the old one. Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant