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

Added Optional Parameter keyboardType in Input Widget #147

Conversation

MuhammadUsamaSiddiqui
Copy link
Contributor

@MuhammadUsamaSiddiqui MuhammadUsamaSiddiqui commented Dec 12, 2020

I have added an optional TextInputType parameter named keyboardType in Input Widget because I am facing issue with iOS soft keyboard. By default iOS number keyboard don't have "Done" button on it. But if I assign TextInputType.numberWithOptions(signed: true, decimal: true) to keyboardType as well as false to formatInput parameters then the iOS will show alpha-numeric keyboard with "Done" button, and due to formatInput: false the field will only accept digits.

Have a look at my Issue: #148

I hope you understand my issue.

Thanks

@MuhammadUsamaSiddiqui MuhammadUsamaSiddiqui marked this pull request as draft December 12, 2020 16:14
@MuhammadUsamaSiddiqui MuhammadUsamaSiddiqui marked this pull request as ready for review December 12, 2020 16:14
@natintosh natintosh merged commit 825a293 into natintosh:develop Dec 19, 2020
@luis901101
Copy link

That soft keyboard is the expected keyboard for number or phone numbers in iOS... bad from Apple not allowing to set a Next, Done, or whatever button for users to hide the keyboard on demand... using keyboardType and formatInput as you comment is not a solution either... because the keyboard becomes useless with that configuration and the phone number formatting is lost…
Any time I have had used a number input field in flutter I have used this package keyboard_actions which allows you to set a toolbar on top of keyboard with some options to change focus or simply hide keyboard…

check this:
https://www.dropbox.com/s/pou0897e8h5joxo/IMG_4617.PNG?dl=0

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

Successfully merging this pull request may close these issues.

3 participants