JMRSDK Development
v4.57
v4.57
  • Jio Mixed Reality SDK Documentation
    • Changelog
      • Upgrade Guide
    • Application Requirements
  • Device Information
    • JioGlass
    • JioDive
  • Supported Smartphones
  • Controller Specifications
    • Physical Controllers
    • External Gamepad
    • Virtual Controller
  • Getting Started
    • Development Platform
    • Setting Up Jio Mixed Reality Project in Unity
    • Video Tutorials
    • URP Support
      • Setting Up Your Project With URP
  • JMRSDK
    • JMRSDK Content
    • JMRMixedReality Prefab
    • System Dock
    • JMRRig
      • Local Rig
      • Setting Homepage (Quit functionality)
    • Webcast
  • Develop
    • Editor Emulator
    • JioGlass Controller Interactions
    • Cameras
    • Tesseract Mixed Reality UI Toolkits
    • In-app purchase
    • Examples
  • Interaction
    • Gaze Interaction
      • Gaze and Click
      • Gaze and Dwell
    • Interaction
      • Pointer Manager
        • Examples
      • Active Input Source
    • Interfaces
      • IFocusable
      • ISelectHandler
      • ISelectClickHandler
      • IBackHandler
      • IHomeHandler
      • IMenuHandler
      • IFn1Handler
      • IFn2Handler
      • ITouchHandler
      • ISwipeHandler
      • IManipulationHandler
    • Controller Input Actions
      • Touchpad - Touch
      • Touchpad - Swipe
      • Source Buttons
      • Manipulation
    • Actions
    • Device State
      • JioDive Device State
      • JioGlass Device State
      • Controller Device State
  • 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
      • App optimization
    • Running your application
      • JioImmerse App For Jio Mixed Reality (JMR) Devices
      • Running the application
      • IPD Calibration
    • Licensing Journey In Android JioImmerse
    • Licensing Journey in iOS JioImmerse
  • Publish
    • Branding Guidelines
    • Signing your App
    • Publishing to Google Play Store
      • Play Store Upload Journey
    • Publishing to JioImmerse Developer Console
    • Publishing to Apple Store
    • iOS Deep linking
  • 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
      • FAQs - iOS
    • FAQs - Running and Publishing
    • Laser Point Not Visible
Powered by GitBook
On this page
  • Introduction to Interaction
  • Interaction
  • InputManager
  1. Interaction

Interaction

PreviousGaze and DwellNextPointer Manager

Last updated 5 months 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.