| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
../../../../../src/osd/modules/input/input_winhybrid.cpp:107:16: error: suggest braces around initialization of
subobject [-Werror,-Wmissing-braces]
: m_variant({0})
|
| | |
|
| |
|
|
|
|
| |
them (SDL normally strips these out)
Don't strip linefeed characters (Ctrl-J) from natural keyboard input except when pasting strings
|
| |
|
|
| |
* Note that the code to map excess buttons to switches doesn't actually do anything useful while INPUT_MAX_BUTTONS and MAX_BUTTONS happen to be defined to the same number.
|
| |
|
|
|
|
|
|
| |
thing as invalid (e.g. A S not A)
ioport.cpp:
* better than 50% reduction in compile time, and better locality for static data
* better encapsulation, const correctness and noexcept usage
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Check that m_display is not null to prevent crash
https://mametesters.org/view.php?id=7372
* Probe method to check if X11 is actually being used
As per: https://github.com/mamedev/mame/pull/5725#issuecomment-540004475 this will help MAME verify X11 has no inputs when X11 is not actually being used (e.g. on RetroPie where SDL display is RPI).
* Fix issue where a lightgun with no name would return nullptr
As suggested by https://github.com/mamedev/mame/pull/5725#issuecomment-539914514 , a bug in create_lightgun_device() returned nullptr if the lightgun had no name. Now it will create the device with a name using the lightgun's device index
* Change older m_display change to assert
This module can now be probed and disabled correctly if X11 is not being used. Removed the if statements that would be called every cycle (and fail silently) in favor of asserts, as MAME does not currently handle dynamic hardware configuration changes.
* Fixing semicolons in asserts that were ifs
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(nw) This has been a long time coming but it's here at last. It should
be easier now that logerror, popmessage and osd_printf_* behave like
string_format and stream_format. Remember the differences from printf:
* Any object with a stream out operator works with %s
* %d, %i, %o, %x, %X, etc. work out the size by magic
* No sign extending promotion to int for short/char
* No widening/narrowing conversions for characters/strings
* Same rules on all platforms, insulated from C runtime library
* No format warnings from compiler
* Assert in debug builds if number of arguments doesn't match format
(nw) Also removed a pile of redundant c_str and string_format, and some
workarounds for not being able to portably format 64-bit integers or
long long.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
existing window (#5381)
* Creating an -attach_window command line parameter on Windows to attach
to an existing window
* Moved -attach_window option to Windows-specific code
* Created an osd_set_aggressive_input_focus() function and exposed to LUA
* Created a dummy implementation of osd_set_aggressive_input_focus() for
SDL
|
| |
|
|
|
|
|
| |
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)
|