- --
Viewing Issue Advanced Details
[ Jump to Notes ]
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
06155 | Interface | Minor | Always | Mar 8, 2016, 08:44 | Jul 6, 2017, 08:36 |
Tester | Zaghadka | View Status | Public | Platform | MESS (Official Binary) |
Assigned To | Resolution | Fixed | OS | Windows Vista/7/8 (64-bit) | |
Status [?] | Resolved | Driver | |||
Version | 0.171 | Fixed in Version | 0.185 | Build | Normal |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 06155: adam, a2600, c128, c64, sms, sms1, nes, snes, snespal, vic1001: Cannot select multiple inputs in some MESS sets | ||||
Description |
When defining controls for the sets included, you cannot pick multiple inputs for the same control. i.e.: You cannot pick Kbd 1 _or_ Joy 1 Button 7 for the start control. When you enter a control the second time, the new control overrides the choice, instead of appending the choice with an "or." This occurs at least in the MESS sets above. It may occur in more; I only tested machines I know you can hook up a joystick. The expected behavior is that the interface will keep appending controls with an "or" statement until you press "delete" and start over. Some sets work, such as aes. I am unsure of the regression version as this is my first time trying out MESS. |
||||
Steps To Reproduce | Launch game, attempt to define multiple controls in the TAB menu. May need to press "scroll lock" to activate the UI (e.g.: in c64). | ||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | adam,a2600,c128,c64,sms,sms1,nes,snes,snespal,vic1001 | ||||
Attached Files
|
|||||
Relationships
There are no relationship linked to this issue. |
Notes
3
No.12441
Zaghadka Tester
Mar 8, 2016, 09:02
|
Seems to affect clones of these sets as well. |
---|---|
No.12445
NekoEd Senior Tester
Mar 8, 2016, 17:41
|
Altered report to remove driver as multiple drivers are referenced. |
No.12447
Tafoid Administrator
Mar 8, 2016, 19:25
|
Looks to be a limitation of those devices which are obtained/used via the slot functions. You can tell if a driver has this by examining -listslots output for any type of controller. Anyway, I confirmed in a few instances listed above. |