| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
On X11 Linux, every lightgun event was passed onto every lightgun
device within MAME. This obviously works for 1 gun, but with 2, it
causes both crosshairs to move in the same direction at the same
time.
|
| |\
| |
| | |
Linux X11 Input: Fix lightgun support
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
SDL/X11 number mouse/lighgun buttons 1,2,3, while windows and other parts of
MAME like offscreen_reload expect 0,2,1. Transpose buttons 2 and 3, and then
-1 the button number to align the numbering schemes.
This fixes lightgun support on Linux - tested with an Ultimarc AimTrak and
the following config:
lightgun 1
lightgun_device lightgun
lightgunprovider x11
lightgun_index1 "Ultimarc Ultimarc"
offscreen_reload 1
Note: MAME must be compiled with XInput support:
make -j10 NO_USE_XINPUT=0
Fixes bug #4695
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
Keymaps must have been broken for ages:
- It is now possible to map every scancode SDL2 defines.
- Removed keycode field. This was a leftover from SDL1.x
- Fixed bug preventing keymaps from working.
- Fixed the DE keymap.
- Converted other keymaps to new format and added a
comment that they have to be reviewed and fixed.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
move between clicks
|
| |
|
|
| |
instead of Z+, placing IPT_PEDAL and IPT_PEDAL2 on separate axes. (nw)
|
| |
|
|
|
|
|
|
| |
not Z Axis+Z Rotation where the axis resting position was at the middle of the trigger (nw)"
The DirectInput Z-axis trigger merger seems more widely considered a bug than a feature, and probably should not be the default MAME behavior.
This reverts commit 80a64430a39f306f702766525a093ac1141f7252.
|
| |
|
|
| |
Axis+Z Rotation where the axis resting position was at the middle of the trigger (nw)
|
| |
|
|
|
|
| |
lag if you keep typing while a big list is searched.
(nw) patch up German translation
|
| | |
|
| |
|
|
| |
Change to snprintf with assert since apparently snprintf fixes the reported problem.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also thread synchronization which will be needed later when we have multiple windows (nw)
|
| |
|
|
| |
* Change window handle storage to template instead of void* (nw)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Use standard uint64_t, uint32_t, uint16_t or uint8_t instead of UINT64, UINT32, UINT16 or UINT8
also use standard int64_t, int32_t, int16_t or int8_t instead of INT64, INT32, INT16 or INT8
|
| |
|
|
| |
utf16_char, unicode_char (nw)
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Add BS, Tab, 00, 000 keys common on add-on keypads as input items; SDL may recognize these, but DirectInput does not
- Assign Keypad 00 and Keypad 000 in several drivers' input lists
- Add SDL keycode for "cancel" key
- Add keypad keys as alternates to natural keyboard
- Move has_keyboard() out of the core; enabled() test is unnecessary now that all optional keyboards are slot devices (nw)
|
| | |\
| | |
| | | |
Adding new string conversion overloads
|
| | | |
| | |
| | |
| | |
| | | |
utf8_from_[a|w|t]string ==> osd::text::from_[a|w|t]string
[a|w|t]string_from_utf8 ==> osd::text::to_[a|w|t]string
|
| | |/ |
|
| | | |
|
| | |\
| | |
| | | |
Adding support for stable controller id's
|
| | | | |
|
| | |/
|/|
| |
| |
| |
| |
| | |
This change generates a more unique device id for derect input devices
by incorporating the product unique identifier and instance unique
identifier. This allows for better disambiguation on device id when
mapping controllers via mapdevice config settings.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This change adds id() property to input_device, which represents the
unique device id. This allows the osd layer when creating a device to
pass a friendly display name along with a unique identifier.
Currently the device id is only used to map a physical controller device
to controller id, but can be used more generally in the future. For raw
input devices, we use the full raw input name as the device id. For all
other devices, we fall back to device name as the device id. The
"uniqueness" of the device id is not currently enforced in code.
|
| |/
|
|
|
|
|
|
| |
This change adds support for configuring device to conrtoller id. This
allows for stable controller ids even if USB devices are plugged /
unplugged, system is rebooted, etc.
See documentation for additional context.
|
| | |
|