[LUA] How to map field values to CFG port "properties"?

[Jakobud]

I'm looking at various ioport field values and wondering how their names map to properties in <port> tags in .cfg files. For example in centiped.cfg I have this

<port tag=":TRACK0_X" type="P1_TRACKBALL_X" mask="255" defvalue="0" keydelta="15" sensitivity="46" reverse="no">
    <newseq type="standard">
        MOUSECODE_1_YAXIS
    </newseq>
    <newseq type="increment">
        KEYCODE_J
    </newseq>
    <newseq type="decrement">
        KEYCODE_K
    </newseq>
</port>

When I use LUA to examine the ioport fields I see things like:

name = Trackball X
type_class = controller
mask = 0xFF
defvalue = 0x0
user_value = 0
minvalue = 0
maxvalue = 255
sensitivity = 50
player = 0
way = 0
is_analog = true
is_digital_joystick = false
enabled = true
cocktail = false
toggle = false
analog_reverse = true
analog_reset = false
analog_wraps = false
analog_invert = false
impulse = 0
crosshair_scale = 1.0
crosshair_offset = 0.0

So I see values like mask field setting maps to "mask" in the .cfg file. Some of these are obvious. But what about the rest? I can see that keydelta represents the Analog Increment/Decrement Speed in the MAME UI, but where is the field for this? How do I access this value in the ioport fields?

Are there methods to map the field settings to the names that show up in .cfg files?

Also in the src I see references to fields delta which I think map to keydelta and something else called centerdelta. But using LUA I cannot access any field settings called delta or centerdelta.

[cuavas]

keydelta and centerdelta aren't exposed to Lua right now, so the simple answer is you can't until I fix it. You aren’t missing anything.

[Jakobud]

Cool thank you for the confirmation.

If it isn't clear by now, what I'm really trying to do is to be able to generate my own .cfg files, with all values for all ioport fields in them.

What I don't love about MAME's current .cfg's is that they only include non-default values in them. If a value for any input or dipswitch is still the default value, it doesn't get included in the .cfg.

It would be amazing if there was an option to force MAME to include ALL values, ALL dipswitches, configs, etc, everything in the .cfg's it generates when you exit a game.

I've been making a LUA plugin to try to do it myself and it's going well so far, but it's just a lot of reverse engineering and obviously not everything is exposed:

https://github.com/Jakobud/configgenerator

Would it be hard to add an option to MAME (just a mame.ini setting) that would make it include everything in the .cfgs?

[cuavas]

Including explicit defaults is problematic because when stuff gets refactored so that the interpretation of values is different, it breaks for absolutely everyone rather than just requiring people who’d changed the setting to update their configuration. It would create too much support burden from people not understanding it.

[Jakobud]

Okay, can you elaborate on that with an example? I'm genuinely curious.

[Jakobud]

Are you saying that when something changes for a rom, that the config file would no longer match the config files that people have in their CFGs and then their inputs would no longer work?

[cuavas]

Yes.

[cuavas]

mamedev/mame@4b0ff80 makes it possible to configure analog input adjustments from scripts. The bindings for analog_reverse and sensitivity should make more sense now.

[Jakobud]

Man you are a machine! So this exposes those missing values to LUA and makes sensitivity show the user defined value?

[cuavas]

Look at the diff to the documentation page to see what changed.

[Jakobud]

That looks great thank you. FYI I think the analog_reverse was already accurately showing the value, but having the explicitly defined default value you grab is helpful.

[Jakobud]

Correction, analog_reverse is also currently showing the default value.

Thanks again for the update. Looking forward to it.