baykovr/AVPI

Accessibility features.

Opened this issue · 2 comments

Firstly, many thanks to @baykovr for developing GAVPI, and to anyone else who contributed. GAVPI can be a very useful tool for playing video games, especially for those without access to lots of other inputs.

Having used GAVPI a fair amount in the field of video game accessibility, I think there are a few features that might make it even more effective in this area. I was planning to make a fork of the project and add those features in time, but before I did, I thought I'd check and see if any of the potential features would be useful for the main project, as they may have benefits elsewhere.

I will list them all here, but will create separate issues for any that you think would be worth including.

1. Add Toggle Hold

Add a "ToggleKey" to the Key/Mouse Press Action that toggles the specified key.

(If key is up, hold down key. If key is down, release key.)

2. Increase Press Duration

The default KeyPress time is too short to be detected by some games, I usually use KeyDown, Wait 100ms, KeyUp instead to be safe. Perhaps it's worth making the default KeyPress 100ms long (standard key press time)? Or an option to set the global KeyPress time of GAVPI?

3. Switch Profile Action

Add an Action that allows you to switch profile.

4. Voice Controllable

Have an option to make GAVPI itself voice controllable.

Saying "file", would drop down the File menu. "open profile", "add trigger" and so on.

Unsure of how well, if at all, this would work.

5. Set Default Profile

Having the ability to associate a program with a GAVPI profile is awesome, but it would be cool if there was just a load profile at startup option as well.

+1

Have an option to make GAVPI itself voice controllable.

sounds interesting

Unsure of how well, if at all, this would work.

Why not?

Have an option to make GAVPI itself voice controllable.

sounds interesting

Unsure of how well, if at all, this would work.

Why not?

I think it could be possible, I think my main concern was that it could interfere with a profile's commands/phrases. If you had one phrase while a profile was running to open the GAVPI interface, and then once it was open to switch to a set of phrases that allow you to control GAVPI, that might work.