blocks|key|1908017|text|我不认为this+answer是正确的。如果我创建了一个新项目，并通过添加以下代码片段仅编辑MainActivity：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1908018|public+boolean+dispatchTouchEvent(MotionEvent+ev)+{
++++View+contentsView+=+findViewById(android.R.id.content);

++++int+test1[]+=+new+int[2];
++++contentsView.getLocationInWindow(test1);

++++int+test2[]+=+new+int[2];
++++contentsView.getLocationOnScreen(test2);

++++System.out.println(test1[1]+%2B+"+"+%2B+test2[1]);

++++return+super.dispatchTouchEvent(ev);
}|code-block|syntax|javascript|1908019|我将看到打印到控制台108+108。这使用的是运行4.3的Nexus+7。我使用运行早在2.2版本的android版本的仿真器也得到了类似的结果。|style|CODE|1908020|正常的活动窗口将使用FILL_PARENTxFILL_PARENT作为其WindowManager.LayoutParams，这将导致它们的布局达到整个屏幕的大小。窗口位于状态栏和其他装饰的下方(关于z顺序，而不是y坐标)，因此我认为更准确的图表应该是：|1908021|%7C--phone+screen-----activity+window---%7C+
%7C--------status+bar-------------------%7C+
%7C+++++++++++++++++++++++++++++++++++++%7C+
%7C+++++++++++++++++++++++++++++++++++++%7C+
%7C-------------------------------------%7C+|1908022|如果您逐句了解这两种方法的源代码，您将看到getLocationInWindow遍历视图的视图层次结构直到RootViewImpl，计算视图坐标并减去父滚动偏移量。在我上面描述的情况下，ViewRootImpl从WindowSession获取状态栏高度，并通过fitSystemWindows将其向下传递给ActionBarOverlayLayout，这会将该值添加到操作栏高度。然后，ActionBarOverlayLayout将这个相加值作为边距应用于其内容视图，该视图是您的布局的父级。|1908023|因此，您的内容布局低于状态栏，不是因为窗口从比状态栏更低的y坐标开始，而是因为将边距应用于您的活动的内容视图。|1908024|如果仔细查看getLocationOnScreen源代码，您会发现它只是调用了getLocationInWindow，然后添加了窗口的左侧和顶部坐标(这些坐标也由ViewRootImpl传递给视图，后者从WindowSession中获取它们)。在正常情况下，这两个值都是零。在某些情况下，这些值可能是非零的，例如，位于屏幕中间的对话框窗口。|1908025|1908026|因此，总结一下:一个正常活动的窗口充满了整个屏幕，甚至状态栏和装饰物下面的空间也是如此。这两个方法将返回相同的x和y坐标。只有在特殊情况下，例如窗口实际偏移的对话框，这两个值才会不同。|1908027|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/17673679^0|4|B|0|0|0|A|7|0|0|0|L|J|0|0|6|J|13|J|0|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@$A|18|B|19|1|1A]]|C|$]]|$1|D|3|E|5|F|7|1B|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|1C|8|@$A|1D|B|1E|K|L]]|9|@]|C|$]]|$1|M|3|N|5|6|7|1F|8|@]|9|@]|C|$]]|$1|O|3|P|5|F|7|1G|8|@]|9|@]|C|$G|H]]|$1|Q|3|R|5|6|7|1H|8|@$A|1I|B|1J|K|L]]|9|@]|C|$]]|$1|S|3|T|5|6|7|1K|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|1L|8|@$A|1M|B|1N|K|L]|$A|1O|B|1P|K|L]]|9|@]|C|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|X|3|Y|5|6|7|1R|8|@]|9|@]|C|$]]|$1|Z|3|-4|5|6|7|1S|8|@]|9|@]|C|$]]]|10|$11|$5|12|13|14|C|$15|16]]]]

I don't think <a href="https://stackoverflow.com/a/17673679">this answer</a> is correct. If I create a new project, and edit only the MainActivity by adding the following snippet:

<pre><code>public boolean dispatchTouchEvent(MotionEvent ev) {
 View contentsView = findViewById(android.R.id.content);

 int test1[] = new int[2];
 contentsView.getLocationInWindow(test1);

 int test2[] = new int[2];
 contentsView.getLocationOnScreen(test2);

 System.out.println(test1[1] + " " + test2[1]);

 return super.dispatchTouchEvent(ev);
}
</code></pre>

I will see printed to the console <code>108 108</code>. This is using a Nexus 7 running 4.3. I have similar results using emulators running android versions as far back as 2.2.

Normal activity windows will have FILL_PARENTxFILL_PARENT as their WindowManager.LayoutParams, which results in them laying out to the size of the entire screen. The Window is laid out underneath (in regards to z-order, not y-coordinates) the statusbar and other decorations, so I believe a more accurate chart would be:

<pre><code>|--phone screen-----activity window---| 
|--------status bar-------------------| 
| | 
| | 
|-------------------------------------| 
</code></pre>

If you step through the source of these two methods, you will see that <code>getLocationInWindow</code> traverses up your view's view hierarchy up to the RootViewImpl, summing view coordinates and
subtracting parent scroll offsets. In the case I described above the ViewRootImpl is getting the status bar height from the WindowSession, and passing it down through fitSystemWindows to the ActionBarOverlayLayout, which adds this value to the actionbar height. ActionBarOverlayLayout then takes this summed value and applies it to its content view, which is the parent of your layout, as a margin.

So, your content is laid out lower than the status bar not as a result of the window starting at a lower y coordinate than the status bar, but instead as a result of a margin being applied to your activity's content view.

If you peer into the <code>getLocationOnScreen</code> source you'll see it merely calls <code>getLocationInWindow</code> and then adds the Window's left and top coords (which are also passed to the View by ViewRootImpl, which fetches them from the WindowSession). In the normal case, these values will both be zero. There are some situations where these values may be non-zero, for example a dialog window that is placed in the middle of the screen.

<hr>

So, to summarize: A normal activity's window fills the entire screen, even the space under the status bar and decorations. The two methods in question will return the same x and y coordinates. Only in special cases such as dialogs where the Window is actually offset will these two values differ.

What is the difference between screen and view in the context of these two methods?

I have a button and I want to get the x coordinate of its center.

I guess this would be enough:

<pre><code>public int getButtonXPosition() {
 return (button.getLeft()+button.getRight())/2;
}
</code></pre>

but then, what difference would it make if I would have used 

<code>getLocationOnScreen()</code> or <code>getLocationInWindow()</code> ?

(adding half of the button's width to that, of course)

getLocationOnScreen() vs getLocationInWindow()

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

在这两种方法的上下文中，屏幕和视图有什么不同？我有一个按钮，我想要得到它中心的x坐标。我想这就足够了：public int getButtonXPosition() {    return (button.getLeft()+button.getRight())/2;}但是，如果我使用了getLocationOnScr...

getLocationOnScreen() vs getLocationInWindow()-腾讯云开发者社区-腾讯云

问getLocationOnScreen() vs getLocationInWindow()
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问getLocationOnScreen() vs getLocationInWindow()EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问getLocationOnScreen() vs getLocationInWindow()
EN