Skip to content
This repository has been archived by the owner on Jun 29, 2023. It is now read-only.

D3VICE button simulation #6

Closed
insanity54 opened this issue Nov 13, 2018 · 2 comments
Closed

D3VICE button simulation #6

insanity54 opened this issue Nov 13, 2018 · 2 comments
Assignees
Labels
core Core functionality that the success of controlpointer depends on

Comments

@insanity54
Copy link
Contributor

insanity54 commented Nov 13, 2018

In the master plan of DooM D3vices, Physical d3vices are optional. A cell phone atop a table can serve as a controlpoint, with large buttons spanning the entire screen.

A user should be able to open the web app, navigate to the Virtual Controlpoint page, and set the phone on a table top. The phone in this state should be functionally equivalent to a DooM D3VICE 2B (2-button hardware d3vice.)

TL;DR: Controlpointer webapp should have press-and-hold D3VICE button simulation for the simulation (#4, #5) functionality.

@insanity54 insanity54 added the core Core functionality that the success of controlpointer depends on label Nov 13, 2018
@insanity54 insanity54 added this to the Time to show off! milestone Nov 13, 2018
@insanity54 insanity54 self-assigned this Nov 13, 2018
@insanity54
Copy link
Contributor Author

In progress. Labelled as "Virtual Controlpoint"

@insanity54
Copy link
Contributor Author

Completed in 7281cf2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
core Core functionality that the success of controlpointer depends on
Projects
None yet
Development

No branches or pull requests

1 participant