| Main > Software Forum |
| Warlords 4 LED (start button) support |
| << < (7/7) |
| Howard_Casto:
I haven't had time. I really wish someone would do this for me, and by "do this" I mean do it properly. This is how mame should be modified. Step1: Remove any and all references to the numlock/scrolllock/capslock still left in the individual drivers and reroute those calls to a led-controlling function. (I beleive this is already done. Step2: Instead of drivers passing "turn on capslock" modify them to a more generic "turn on virtual output #1" Step3: The led status function needs to be modified to allow more methods of output... the easiest being the "cheap" parallel port method. Also adding in support for randy's new interface and any others that are to become a standard. Step4: Look at the code mame uses to read in ctrlr files and copy it, only this time make it an output file. This file should have the following "virtual outputs": CoinLight1 CoinLight2 CoinLight3 CoinLight4 Light1 Light2 Light3 Light4 Light5 Light6 Light7 Light8 Light9 Light10 Solenoid1 Solenoid2 Solenoid3 Solenoid4 Solenoid5 Solenoid6 Solenoid7 Solenoid8 Solenoid9 Solenoid10 Motor1 Motor2 Motor3 Motor4 Motor5 Motor6 Motor7 Motor8 Motor9 Motor10 Misc1 Misc2 Misc3 Misc4 Misc5 Misc6 Misc7 Misc8 Misc9 Misc10 Of course which driver uses which types of inputs is pretty self-explainatory. Virtual outputs are useless without the proper "real life" outputs to bind them to. Initially I suggest the following constants: CapsLock NumLock ScrollLock Parallel1 Parallel2 Parallel3 Parallel4 Parallel5 Parallel6 Parallel7 Parallel8 LedWhiz1 (there's no way I'm listing all 50 inputs) Also including any other input methods available. For windows I would also suggest The force feedback motors, which have a specific usb name I don't know of off hand. Final Step: Bring everything together. Drivers would now send the proper virtual output type to the led function (in most cases coin1 coin2, ect..) the modified ctrlr files woudl have already binded said constant to a real output and thus the led function would manipulate the proper device. This is a lot of coding sure, but if done this way, when a new fangled light driver like randy's pops up, support in mame can be added literally in a day or so. I know how to do the modifications in sheer logic, but in all honesty my C skills aren't up to the chllenge of dong so many code changes to the core. I however would be willing to help someone else, as I know how to write most of the input/output functions in a way mingw can handle. |
| Navigation |
| Message Index |
| Previous page |