🤩
JMRSDK Development
v4.27.10
v4.27.10
  • Tesseract Mixed Reality SDK Documentation
    • Changelog - 4.27.10
  • Device Information
    • Device Specification
    • Controller Specifications
      • Physical Controllers
      • Virtual Controller / Virtual Keyboard for JioGlass
  • Getting Started
    • Development Platform
    • Setting Up A Jio Mixed Reality Project in Unity
    • URP Support
      • Setting Up Your Project With URP
      • Reverting Back to Built-In Render Pipeline
  • JMRSDK
    • JMRSDK Content
    • JMRMixedReality Prefab
    • JMRRig
      • Local Rig
      • Setting Homepage (Quit functionality)
      • Recenter Application on Resume
  • Develop
    • Editor Emulator
    • JioGlass Controller Interactions
    • Cameras
    • Jio Mixed Reality UI Toolkits
    • Examples
  • Interaction
    • Gaze and Dwell
    • Interaction
      • JioGlass Lite Interaction
      • Jio Prism(Holoboard) Interaction
      • Jio Dive Interaction
      • Pointer Manager
        • Examples
    • Interfaces
      • ISelectHandler
      • ISelectClickHandler
      • IFocusable
      • ISwipeHandler
      • ITouchHandler
      • IBackHandler
      • IHomeHandler
      • IMenuHandler
      • IVoiceHandler
      • IFn1Handler
      • IFn2Handler
      • IManipulationHandler
    • Controller Input Actions
      • Touchpad - Touch
      • Touchpad - Swipe
      • Source Buttons
      • Manipulation
    • Actions
    • Device State
      • Device Connected
      • Device Disconnected
      • Battery percentage update
      • Scanning for Device
      • Battery Percentage
  • Voice
    • Voice
      • Speech Events
      • Speech Result
      • Speech Error
      • Speech Session End
      • Speech Cancel
    • Listening
  • Tracking
    • Tracking
      • Coordinate System
    • Tracking Framework
      • TrackerManager Actions
        • Get Head Position
        • Get Head Rotation
        • Get Head Transform
      • TrackerManager Methods
        • Get Head Position
        • Get Head Rotation
        • Get Head Transform
    • Recenter
  • Building and Testing
    • Building to Target Device
      • Merging AndroidManifest
      • Performance Optimization
    • Companion App For Jio Mixed Reality (JMR) Devices
      • Running the application on Prism (Holoboard)
    • IPD Calibration
  • Publish
    • Signing App for App Store
    • Publishing to JioGlass Developer Console
    • Developer Console Analytics
  • Capturing and Recording
    • Capture Videos and Screenshots
      • Capturing Screenshot/Videos using scrcpy
      • Capturing Screenshot/Videos using Vysor
  • Troubleshooting
    • FAQs - Develop
    • FAQs - Building to device
      • Gradle
      • Old aaptOptions error fix
    • FAQs - Running and Publishing
    • Laser Point Not Visible
Powered by GitBook
On this page
  • Introduction to Interaction
  • Interaction
  • InputManager
  1. Interaction

Interaction

PreviousGaze and DwellNextJioGlass Lite Interaction

Last updated 2 years ago

Introduction to Interaction

Interactions are defined as how the user interacts with the content in the JioGlass. Interactions in the Mixed Reality space are done differently than how we are used to in current mobile devices. Having the ability to interact with content brings a new sphere of immersive for the users to experience. The various form of interactions includes – controller interaction, hand interaction, and eye-gaze interaction. Interactions in the current environment of JMRSDK are done using the JioGlass Controller. The controller must be successfully connected. If the controller gets disconnected user needs to scan and connect to the nearby controller to have a smooth experience. The JMR Interaction Manager handles the core functionalities of verifying connection, disconnection of the controller, returning its battery percentage, and scanning for controllers if disconnected.

Interaction

Interaction is responsible for managing all swipe, touch, select, and click events.

InputManager

The input Manager is responsible for managing input sources and dispatching relevant events to the appropriate input handlers.