Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M
Monado
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 45
    • Issues 45
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 15
    • Merge Requests 15
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Monado
  • Monado
  • Issues
  • #107

Closed
Open
Opened Dec 02, 2020 by Ryan Pavlik@ryan.pavlikOwner0 of 1 task completed0/1 task

Follow-up from "Android: Initial out of process support and Monado Service."

The following discussion from !609 (merged) should be addressed:

  • @ryan.pavlik started a discussion: (+2 comments)

    these changes to make nativePointer optional worry me, because the next step is to call a native method on the various surface callbacks as well as on activity lifecycle callbacks, which will struggle if there's no nativeCounterpart available. I'll step through the commits here and see if I can figure out why this was needed (why a native-based creation wasn't working) and how it might be fixed.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: monado/monado#107