| Main > Software Forum |
| What is Mame's "generic output support system" capable of? |
| << < (5/5) |
| 2600:
--- Quote from: Howard_Casto on January 31, 2007, 03:30:19 pm --- This is definately an issue, but I think it can be better handled on the client end. The easiet way is to have "time outs" for objects that can be damaged if left on. So if the client app is routing a bit of data to a solenoid, and the solenoid is left on for more than, say, three seconds, the app automatically sets the value back to 0 and turns it off. Having lights say on wouldn't hurt, so the only issues you are going to run into involve force feedback and solenoids. Doing it in mame would be more complicated because the output function doesn't poll the values of outputs, rather the value to be set is passed to it. So when you paused you could definately have the function set everything to 0, but I dunno how you could easily, and universally get all of the values back once you un-pause. --- End quote --- Yeah, that's definitely one way to do it. Originally, I was thinking the client app could remember the state of the outputs and return them when unpaused. I only wanted MAME to let the client know the system has paused. Technically, if I were to implement a client I would implement the timeout even if MAME had a pause message as a dual fail safe. Of course, I was also thinking that knowing when MAME is paused would could be quite useful. |
| headkaze:
I have written a dll that deals with all the messaging, and I will be releasing it soon for developers. |
| Howard_Casto:
Sit tight everyone. Using the latest programming techniques, the best hardware available, and a box of crayons, I think hk has a working dll and we've worked out all the kinks with the example code. |
| Navigation |
| Message Index |
| Previous page |