|
4 | 4 | <meta charset="UTF-8"> |
5 | 5 | <meta name="viewport" content="width=device-width,initial-scale=1"> |
6 | 6 | <meta name="turbo-root" content="/CodeGRITS"> |
7 | | - <meta name="turbo-cache-control" content="no-cache" data-turbo-track="reload" data-track-token="3.5.0.764995187358"> |
| 7 | + <meta name="turbo-cache-control" content="no-cache" data-turbo-track="reload" data-track-token="3.5.0.767222795539"> |
8 | 8 |
|
9 | 9 | <!-- See retype.com --> |
10 | 10 | <meta name="generator" content="Retype 3.5.0"> |
|
32 | 32 | <script data-cfasync="false">(function () { var el = document.documentElement, m = localStorage.getItem("doc_theme"), wm = window.matchMedia; if (m === "dark" || (!m && wm && wm("(prefers-color-scheme: dark)").matches)) { el.classList.add("dark") } else { el.classList.remove("dark") } })();</script> |
33 | 33 |
|
34 | 34 | <link href="../favicon.png" rel="icon"> |
35 | | - <link href="../resources/css/retype.css?v=3.5.0.764995187358" rel="stylesheet"> |
| 35 | + <link href="../resources/css/retype.css?v=3.5.0.767222795539" rel="stylesheet"> |
36 | 36 |
|
37 | | - <script data-cfasync="false" src="../resources/js/config.js?v=3.5.0.764995187358" data-turbo-eval="false" defer></script> |
| 37 | + <script data-cfasync="false" src="../resources/js/config.js?v=3.5.0.767222795539" data-turbo-eval="false" defer></script> |
38 | 38 | <script data-cfasync="false" src="../resources/js/retype.js?v=3.5.0" data-turbo-eval="false" defer></script> |
39 | | - <script id="lunr-js" data-cfasync="false" src="../resources/js/lunr.js?v=3.5.0.764995187358" data-turbo-eval="false" defer></script> |
| 39 | + <script id="lunr-js" data-cfasync="false" src="../resources/js/lunr.js?v=3.5.0.767222795539" data-turbo-eval="false" defer></script> |
40 | 40 | </head> |
41 | 41 | <body> |
42 | 42 | <div id="docs-app" class="relative text-base antialiased text-gray-700 bg-white font-body dark:bg-dark-850 dark:text-dark-300"> |
@@ -307,6 +307,23 @@ <h4> |
307 | 307 | as <code v-pre>same</code>. This approach significantly reduces storage space. In a previous debugging study, we set the eye-tracking |
308 | 308 | device's sample frequency to 60Hz, and during the 20-minute experiment, the eye-tracking data amounted to only about |
309 | 309 | 40MB.</p> |
| 310 | +<doc-anchor-target id="q7-which-eye-gazes-can-be-analyzed-and-can-gazes-on-the-ui-be-understood"> |
| 311 | + <h4> |
| 312 | + <doc-anchor-trigger class="header-anchor-trigger" to="#q7-which-eye-gazes-can-be-analyzed-and-can-gazes-on-the-ui-be-understood">#</doc-anchor-trigger> |
| 313 | + <span>Q7. Which eye gazes can be analyzed, and can gazes on the UI be understood?</span> |
| 314 | + </h4> |
| 315 | +</doc-anchor-target> |
| 316 | +<p>In CodeGRITS, we only analyze gazes within the code editor. For example, in the following figure, only gazes within the |
| 317 | +red rectangle are mapped to the source code tokens and performed the upward traversal of the AST. For gazes outside the |
| 318 | +code editor, such as those on the file explorer, menubar, tool window, console, etc., we only record their raw |
| 319 | +information and add a remark <code v-pre>Fail | Out of Text Editor</code>. CodeGRITS cannot understand the semantics of gazes on the UI.</p> |
| 320 | +<div style="text-align: center;"> |
| 321 | + <img src="../static/range.png" style="max-width: 100%; width:900px; height: auto;"><br><br> |
| 322 | +</div> |
| 323 | +<p>However, if certain UI elements within the editor are triggered, such as the list for auto-completion or the inline |
| 324 | +definition display, CodeGRITS mistakenly interprets the gaze as being directed at the code content below the UI (when it |
| 325 | +should actually be on the UI). We have not yet found an appropriate method to resolve this issue, which may lead to |
| 326 | +inaccuracies in some gaze analyses.</p> |
310 | 327 |
|
311 | 328 |
|
312 | 329 | <!-- Required only on API pages --> |
|
0 commit comments