Closed xingstarx closed 8 years ago
Do you think it is necessary to use VIewCompat.getPaddingStart()? After my test I can think of two ways is ok
You are right , I will modify it in this weekend. thanks
afater my test ,when set paddingLeft or paddingStart in layout xml ,VIewCompat.getPaddingStart() value is same , when paddingLeft and paddingStart all set, the value we get by VIewCompat.getPaddingStart() is paddingStart
and below Build.VERSION_CODES.JELLY_BEAN_MR1 , not support rtl
and now , you need code review my code ...
If there is a bug, please tell me
should I need to rebase commit record?
Looks good, I'll accept the changes. This only solves the problem of Alignment, however, the text is still display Left to Right. We could easily change this to display text Right to Left, however, some languages like Arabic, are written Right to Left, but their numbers are written Left to Right. Then other languages like Hebrew have text and numbers written right to left.
Since the widget supports both text and numbers, I'm not sure how to handle this currently.
These changes have been deployed in release v1.1 along with updating the code to build for Android API 24.
In our team, we don't deal with special text and numbers Our products are Shou (https://play.google.com/store/apps/details?id=tv.shou.android)
it support rtl
As you said, it only solves the problem of Alignment.
I have an idea, FaceBook AccountKit with PinEntryEditText has a similar function https://developers.facebook.com/docs/accountkit/android You can run Facebook AccountKit sample , check Is it necessary to support text and numbers. and I will check next Monday
ps: my english is very poor,hope you do not mind.
I think this feature is need for this repo