{"action":"opened","issue":{"url":"https://api.github.com/repos/thestonefox/VRTK/issues/705","repository_url":"https://api.github.com/repos/thestonefox/VRTK","labels_url":"https://api.github.com/repos/thestonefox/VRTK/issues/705/labels{/name}","comments_url":"https://api.github.com/repos/thestonefox/VRTK/issues/705/comments","events_url":"https://api.github.com/repos/thestonefox/VRTK/issues/705/events","html_url":"https://github.com/thestonefox/VRTK/issues/705","id":186231136,"number":705,"title":"Permit UI interaction on desktop display while using UI Pointer in VR.","user":{"login":"jeremedia","id":240723,"avatar_url":"https://avatars.githubusercontent.com/u/240723?v=3","gravatar_id":"","url":"https://api.github.com/users/jeremedia","html_url":"https://github.com/jeremedia","followers_url":"https://api.github.com/users/jeremedia/followers","following_url":"https://api.github.com/users/jeremedia/following{/other_user}","gists_url":"https://api.github.com/users/jeremedia/gists{/gist_id}","starred_url":"https://api.github.com/users/jeremedia/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeremedia/subscriptions","organizations_url":"https://api.github.com/users/jeremedia/orgs","repos_url":"https://api.github.com/users/jeremedia/repos","events_url":"https://api.github.com/users/jeremedia/events{/privacy}","received_events_url":"https://api.github.com/users/jeremedia/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-10-31T08:44:22Z","updated_at":"2016-10-31T08:44:22Z","closed_at":null,"body":"Currently interaction with a screen-space overlay canvas is disabled when the UI Pointer component is active as the UI Pointer disables the Standalone Input Module and enables the VRTK Event System VR Input. \r\n\r\nIt is desirable to have mouse-based input remain available to users not in VR for a variety of reasons. Two examples: guided therapy applications where a facilitator controls the experience to support therapeutic goals, and \"asymmetric\" games where local players compete or collaborate with different views and inputs within a shared world.\r\n\r\nIn a conversation on the Unity forums concerning how Unity's EventSystem currently supports only one active Input Module a user shares a solution:\r\n\r\nhttps://forum-old.unity3d.com/threads/multiple-processing-inputmodules.369578/#post-2611925\r\n\r\nDoes this look viable to in the context of VRTK's approach?"}}
{"actor":{"display_login":"jeremedia"}}