Allow axes and buttons to be mapped to the same key via UI about mgba HOT 20 CLOSED

The config.ini file is in a standard location, I don't think there's a need to show the user where that is.

from mgba.

By not having any indication of this functionality in the UI, users won't know that it's an option unless they go digging through the ini files. Most have no clue what ini files are. It's essentially making it a dead feature outside of the pre-configured defaults.

from mgba.

I completely agree, I was just defending the decision to not disclose the location of the config.ini file, since it's in a standard location. That's all :)

from mgba.

The only reason I haven't done this yet is because I haven't figured out what the UI for this should look like. I think there's an open ticket for it in bugzilla, but I'm not sure.

from mgba.

You could go simple. Turn off the auto-progression to the next button and just keep allowing users' inputs to record. Separate the inputs by commas. "4, +1" something like that. You'd need the ability to clear individual buttons, though.

from mgba.

It might also be a good time to work on the UI stuff for hats ( https://endrift.com/mgba/bugs/show_bug.cgi?id=144 ). Wasn't it decided to use arrows for them? ^1, v1, <2, >2

from mgba.

I can use the actual Unicode arrows, you realize. The core doesn't support mapping hats at the moment, though. They're all hard coded to the dpad.

from mgba.

The bigger problem is UNmapping one or the other though, not supporting setting both.

from mgba.

Higan has a decent setup for controller mapping. It's not Qt, but it's a nice concept. https://gitlab.com/higan/higan

from mgba.

You could use a datagrid to handle multiple button assignments. I've seen it done with the OnePAD plugin on PCSX2. Maybe as an advanced config UI? My 2c.

from mgba.

Actually, this is a better link for Higan http://board.byuu.org/phpbb3/viewtopic.php?f=4&t=536

from mgba.

Yes, I'm well familiar with higan :P That said, I may just add "Unmap" buttons for now. I was thinking about doing a much more in-depth UI for 0.3, but that's obviously delayed for now.

from mgba.

He has a "reset" button for clearing all bindings and a "clear" button for clearing the active button's bindings. It works well for multiple mappings.

from mgba.

Partially implemented in a08f092

from mgba.

This works, but the auto-progression skips the leftmost options. Not sure how to fix that without mandating two bindings per button.

from mgba.

I'm not sure what you mean. Leftmost? They should all be equivalent. That said, you can click on a field again to set that value in specific.

from mgba.

Right, that's what I ended up doing. The issue is with auto-progression skipping mapping button entries and only mapping axes before moving onto other buttons like A and B.

This could be fixed by having auto-progression do a second pass or wait for a double entry before moving on, but that would mandate two bindings, unless pressing the same key twice made it think "oh, they're only using buttons or only using axes. move on"

from mgba.

Also, with the current implementation, only people who know the marking conventions of mGBA can intuitively use it. One way to fix this is to have a message appear saying "D Pad" while mapping a button entry and "Joystick" for an axis. But that'll also create anger and frustration with controllers that use hats for D Pads.

from mgba.

However, the double entry wouldn't make sense if those contextual messages appear. A better solution might be to have two D Pads in the UI. One labeled "D Pad" and one labeled "Joystick". They'd each initiate auto-progression for their four directions, but not move onto the other D Pad. That way users can clearly see what they're binding and skip what they don't have. And eventually, the "D Pad" option can integrate hats as an alternative to buttons.

from mgba.

This is basically done now, minus the hats. That's covered by https://endrift.com/mgba/bugs/show_bug.cgi?id=144 though.

from mgba.