We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
继承ViewGroup 定义新的布局文件不是人们所熟悉的,大部分人会被你这个继承吓走了,如何深入了解你的实现,如何更好地去使用呢?
从基本布局入手FrameLayout 才是最好的选择,使用margin 来定位每个View。
/** * 计算显示9 张图片每一张图片的margin * @return [marginLeft, marginRight] */ public static int[] getCircleImageMargin(int imageSize,int count) { //计算坐标 int x, y; switch (count) { case 0: case 1: case 2: y = 0; break; case 3: case 4: case 5: y = 1; break; default: y = 2; } switch (count) { case 0: case 3: case 6: x = 0; break; case 1: case 4: case 7: x = 1; break; default: x = 2; } int left = (imageSize + DimenUtils.dip2px(App.sInstance, 2)) * x; int top = (imageSize + DimenUtils.dip2px(App.sInstance, 2)) * y; return new int[]{left, top}; }
The text was updated successfully, but these errors were encountered:
继承ViewGroup 定义新的布局文件不是人们所熟悉的,大部分人会被你这个继承吓走了,如何深入了解你的实现,如何更好地去使用呢? 从基本布局入手FrameLayout 才是最好的选择,使用margin 来定位每个View。 /** * 计算显示9 张图片每一张图片的margin * @return [marginLeft, marginRight] */ public static int[] getCircleImageMargin(int imageSize,int count) { //计算坐标 int x, y; switch (count) { case 0: case 1: case 2: y = 0; break; case 3: case 4: case 5: y = 1; break; default: y = 2; } switch (count) { case 0: case 3: case 6: x = 0; break; case 1: case 4: case 7: x = 1; break; default: x = 2; } int left = (imageSize + DimenUtils.dip2px(App.sInstance, 2)) * x; int top = (imageSize + DimenUtils.dip2px(App.sInstance, 2)) * y; return new int[]{left, top}; }
麻烦大哥写个能用的,wtf!
Sorry, something went wrong.
... 不知道该怎么吐槽了 给您劈个叉吧
No branches or pull requests
继承ViewGroup 定义新的布局文件不是人们所熟悉的,大部分人会被你这个继承吓走了,如何深入了解你的实现,如何更好地去使用呢?
从基本布局入手FrameLayout 才是最好的选择,使用margin 来定位每个View。
The text was updated successfully, but these errors were encountered: