In addition to the Android player settings, Chrome OS has the following Player Settings.
| 設定 | 機能 | |
|---|---|---|
| Target Architectures | Specify which target architecture you want to support. To support all Chrome OS devices, select both options as the build target. | |
| x86 (Chrome OS) | Support Chrome OS, 32-bit x86 architecture. | |
| x86–64 (Chrome OS) | Support Chrome OS, 64-bit x86–64 architecture. | |
| TargetDevices | アプリケーションの実行可能デバイスを指定します。 | |
| All Devices | すべてのデバイスでアプリケーションを実行可能にします。 | |
| Phones, Tablets, and TV Devices Only | Android の携帯電話、タブレット、TV デバイスのみでアプリケーションを実行可能にします。 | |
| Chrome OS Devices Only | Allow your application to run on Chrome OS devices only. If this option is selected, all Android phones and tablets are not supported. | |
| Chrome OS Input Emulation | Convert all mouse and touchpad events into touchscreen events. This setting is enabled by default. Enable this setting if you developed your application for Android and you want it to work on Chrome OS without any extra development. Disable this setting if you want your application to fully support and receive events directly from input devices such as mice and touchpads. |
|
The Android window-related Player Settings are important because Chrome OS has a desktop windowing user interface. You can use these settings to allow your application to start full-screen or in a window, determine the starting and minimum sizes of the window, and whether it is resizable or not. Only a single aspect ratio - either landscape or portrait - is allowed via auto-rotation.
For optimum performance, allow portrait orientation or landscape orientation, but not both. To avoid several known issues with app rotation and windowing, enable the Resizable Window setting. This setting ensures that windowed applications on Chrome OS can be resized when they aren’t in full-screen mode.
Note: Set your application’s Minimum API Level (menu:File > Build Settings > Player Settings > Other Settings) to at least 24 for windows settings to take effect.