A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developers.google.com/vr/reference/android/com/google/vr/sdk/base/Constants below:

Constants | Google VR | Google for Developers

Constants

Stay organized with collections Save and categorize content based on your preferences.

Static class containing useful constants.

Constants String CARDBOARD_CATEGORY Apps that use the Google VR SDK and run on Cardboard should include this category (along with action MAIN) in their AndroidManifest.xml. String DAYDREAM_CATEGORY Apps that use the Google VR SDK and require Daydream should include this category (along with action MAIN) in their AndroidManifest.xml. String DAYDREAM_CONTROLLER_OPTIONAL_CATEGORY Apps that use the Google VR SDK and support Daydream but can be used without a controller should include this category (along with action MAIN) in their AndroidManifest.xml. String VERSION The Google VR SDK version. Inherited Methods From class java.lang.Object boolean final Class<?>

getClass()

int

hashCode()

final void

notify()

final void

notifyAll()

String

toString()

final void

wait(long arg0, int arg1)

final void

wait(long arg0)

final void

wait()

Constants public static final String CARDBOARD_CATEGORY

Apps that use the Google VR SDK and run on Cardboard should include this category (along with action MAIN) in their AndroidManifest.xml. An Activity tagged with this category will show up in the list of Cardboard apps in the Cardboard launcher. If an app supports both Cardboard and Daydream it should include both intent filters.

Example intent filter:

<intent-filter>
   <action android:name="android.intent.action.MAIN" />
   <category android:name="com.google.intent.category.CARDBOARD" />
 </intent-filter>
 

Constant Value: "com.google.intent.category.CARDBOARD"

public static final String DAYDREAM_CATEGORY

Apps that use the Google VR SDK and require Daydream should include this category (along with action MAIN) in their AndroidManifest.xml. An Activity tagged with this category will show up in the list of Daydream apps in the Daydream launcher. If an app supports both Cardboard and Daydream it should include both intent filters.

Example intent filter:

<intent-filter>
   <action android:name="android.intent.action.MAIN" />
   <category android:name="com.google.intent.category.DAYDREAM" />
 </intent-filter>
 

Constant Value: "com.google.intent.category.DAYDREAM"

public static final String DAYDREAM_CONTROLLER_OPTIONAL_CATEGORY

Apps that use the Google VR SDK and support Daydream but can be used without a controller should include this category (along with action MAIN) in their AndroidManifest.xml. This is similar to the DAYDREAM category, but an app with this category may be launched without a controller being connected, and should use gaze-based interaction or other controllerless interaction systems unless a controller is connected. The user can connect a controller at any time, even after an app is started, so the app should be able to switch to using the controller for input at any time. Additionally, since the user is unable to recenter without a controller connected, the app should ensure that when it starts, the content is in front of the user.

Any app that specifies this should also include the DAYDREAM category, and should act the same as a regular Daydream app if a controller is connected.

Example intent filter:

<intent-filter>
   <action android:name="android.intent.action.MAIN" />
   <category android:name="com.google.intent.category.DAYDREAM" />
   <category android:name="com.google.intent.category.DAYDREAM_CONTROLLER_OPTIONAL" />
 </intent-filter>
 

Constant Value: "com.google.intent.category.DAYDREAM_CONTROLLER_OPTIONAL"

public static final String VERSION

The Google VR SDK version.

Constant Value: "1.206.0"

All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2024-10-09 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-09 UTC."],[[["The `Constants` class provides string constants for declaring Google VR app categories in `AndroidManifest.xml`."],["`CARDBOARD_CATEGORY` and `DAYDREAM_CATEGORY` identify apps for Cardboard and Daydream, respectively, within their launchers."],["`DAYDREAM_CONTROLLER_OPTIONAL_CATEGORY` indicates Daydream support with optional controller usage, requiring alternative interaction methods."],["`VERSION` stores the current version of the Google VR SDK."]]],["The `Constants` class defines key strings for the Google VR SDK. Apps using the SDK should include specific categories in their `AndroidManifest.xml`: `CARDBOARD_CATEGORY` for Cardboard support, `DAYDREAM_CATEGORY` for Daydream, and `DAYDREAM_CONTROLLER_OPTIONAL_CATEGORY` for Daydream without requiring a controller. These categories, along with action MAIN, enable the apps to appear in respective launchers. It also contains the string `VERSION` which defines the current Google VR SDK version.\n"]]


RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4