TASEmulators / TASEmulators/BizHawk
`VirtualPadTargetScreen`s and `VirtualPadAnalogButton`s don't work
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2.8k
- Forks
- 468
- PR merge metrics
- No merged PRs in 30d
Description
Tested with melonDS, unbound the TouchX/Y axes from the mouse and the Virtual Pad still didn't work. The buttons and Mic Volume slider worked. edit: I swear I saw the input display change with the slider on 2.11.1, but CNR.
VirtualPadAnalogStick seems to work (tested with Ares64).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with melonDS using VirtualPadTargetScreens and VirtualPadAnalogButtons after unbinding the TouchX/Y axes from the mouse. Compare their behavior with the working VirtualPadAnalogStick tested with Ares64, and consider the issue done when the target screens and analog buttons respond while the already-working buttons and analog stick remain functional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100