> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos/jiang-windows-she-wei-zhan-ju-zheng-ge-ying-mu.md).

# 將 Windows 設為佔據整個螢幕

您可以將 Windows 設定為佔據整個螢幕，使其看上去像是在使用一台 Windows PC。在全螢幕 (Full Screen) 模式中，會隱藏 macOS 與所有的 Parallels Desktop 控制項。

選擇以下其中一種方法切換為全螢幕 (Full Screen) 模式：

* 從融合 (Coherence) 模式按一下功能表列中的 Parallels Desktop 圖示，然後選擇「**查看**」>「**退出融合 (Coherence)**」。然後按一下「**檢視**」功能表並選擇「**進入全螢幕 (Full Screen)**」模式。
* 從視窗模式，選擇「**查看**」>「**進入全螢幕模式**」或按一下虛擬機器視窗左上角的全螢幕模式圖示 (綠色) 。

<figure><img src="https://content.gitbook.com/content/hzcj9yKOKgjEsgwHkTST/blobs/CyWHiwHmdmhjUzimrHnQ/Screenshot%202024-01-08%20at%2017.36.50.png" alt=""><figcaption></figcaption></figure>

選擇以下其中一種方法退出全螢幕 (Full Screen) 模式：

* 按下 Command-Control-F。
* 移動指標到螢幕頂部直到 macOS 功能表列出現，並按一下「**檢視**」>「**結束全螢幕**」。如果您使用針對遊戲最佳化的「全螢幕」，按下 Control-Option (Alt) 以顯示 Mac 功能表列。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.parallels.com/landing/pdfm-ug/v26-zh-tw/parallels-desktop-for-mac-26-shi-yong-zhi-nan/zai-mac-shang-shi-yong-windows/she-ding-windows-ru-he-shi-yong-macos/jiang-windows-she-wei-zhan-ju-zheng-ge-ying-mu.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.