Unexpected <newseq> values in mame default.cfg?

[arzoo]

I'm hoping someone can help me out with some unexpected input values I'm seeing in a MAME default.cfg file. The default.cfg file I've been provided (by a LEDBlinky user) has some nodes like this:

Code: [Select]

            <port type="P1_JOYSTICKRIGHT_UP">
                <newseq type="standard">
                    KEYCODE_I OR KEYCODE_3_RIGHT KEYCODE_3_UP OR JOYCODE_1_XAXIS_RIGHT_SWITCH JOYCODE_1_YAXIS_UP_SWITCH
                </newseq>
            </port>

There's two things strange about the <newseq> node;
First, what input is KEYCODE_3_RIGHT? Usually a keyboard input would be KEYCODE_<key>, not KEYCODE_<n>_<key>. Is <n> some index for the keyboard?
And second, multiple input codes are usually separated by "OR", but in this example there are two input codes separated with just a space.
JOYCODE_1_XAXIS_RIGHT_SWITCH JOYCODE_1_YAXIS_UP_SWITCH
Does the space indicated something different than the OR?

I can't find any mame documentation that describes the current .cfg xml schema. Can anyone explain or point me in the right direction? Thanks!

[arzoo]

Never-mind, I figured it out. <n> is the keyboard index when multiple keyboard (or encoders are used) and inputs without an OR are combined (like joystick diagonal). Seems obvious now.