match_parent和fill_parent的区别

最新推荐文章于 2023-02-23 09:19:02 发布

金谜闹剧

最新推荐文章于 2023-02-23 09:19:02 发布

阅读量673

点赞数

分类专栏：安卓学习笔记文章标签：屏幕适配 android

本文链接：https://blog.csdn.net/qq_28022735/article/details/51991409

版权

安卓学习笔记专栏收录该内容

11 篇文章 0 订阅

订阅专栏

温故而知新。

They're the same thing (in API Level 8+). Use match_parent.

FILL_PARENT (renamed MATCH_PARENT in API Level 8 and higher), which means that the view wants to be as big as its parent (minus padding)

...

fill_parent: The view should be as big as its parent (minus padding). This constant is deprecated starting from API Level 8 and is replaced by match_parent.

其实很简单，fill_parent在API 8以上就被谷歌弃用了，改名为match_parent。

如果要问为什么，再看：

Google changed the name to avoid confusion.

Problem with the old name fill parent was that it implies its affecting the dimensions of the parent, while match parent better describes the resulting behavior - match the dimension with the parent.

Both constants resolve to -1 in the end, and so result in the identical behavior in the app. Ironically enough, this name change made to clarify things seems to have added confusion rather than eliminating it.

谷歌修改这个名字是为了避免出现冲突，fill_parent有可能在获取父类布局尺寸的时候会出现问题，match_parent能更好的解决这个问题。

（有点讽刺的是，修改名称好像增加了混乱哈哈）