Hi there..
I've been using MP for some time, and had this in the back of my mind for a long time, so i thought i'd share it
When you want to map a key to do something in MP, you have to find the key and then assign it an action from a huge huge list of actions...
Now, most applications that support key-mapping, usually do it the other way round, i.e. 99% of all games give you in the control configuration the Actions list (like fire, jump, move forward etc etc) and you just click the button you want for that job, and it's assigned.
Usability wise, this is also better for the users, what's really important is mapping the MP actions to keys, whereas now you map the keys to actions.
I guess this is a front-end issue, (the back end where the keys are stored and proccessed should stay the same). So a change in the logic in the configuration.exe is all that should be needed to implement this idea.
An idea for implementing this is just give a list of all the actions, along with a description for each of them, and then support let's say up to 3-4 possible keys for each action (for users that have a keyboard, mouse, remote or gamepad). This way, the setup process will also be simplified, since right now to configure MP you have to setup your remote, gamepad and keyboard mappings from separate places.
I can't do any development in C#, so this is out of my league... so it's up to the good devs to tell us...
What do you think of the idea???
I've been using MP for some time, and had this in the back of my mind for a long time, so i thought i'd share it
When you want to map a key to do something in MP, you have to find the key and then assign it an action from a huge huge list of actions...
Now, most applications that support key-mapping, usually do it the other way round, i.e. 99% of all games give you in the control configuration the Actions list (like fire, jump, move forward etc etc) and you just click the button you want for that job, and it's assigned.
Usability wise, this is also better for the users, what's really important is mapping the MP actions to keys, whereas now you map the keys to actions.
I guess this is a front-end issue, (the back end where the keys are stored and proccessed should stay the same). So a change in the logic in the configuration.exe is all that should be needed to implement this idea.
An idea for implementing this is just give a list of all the actions, along with a description for each of them, and then support let's say up to 3-4 possible keys for each action (for users that have a keyboard, mouse, remote or gamepad). This way, the setup process will also be simplified, since right now to configure MP you have to setup your remote, gamepad and keyboard mappings from separate places.
I can't do any development in C#, so this is out of my league... so it's up to the good devs to tell us...
What do you think of the idea???
Cyprus