ac855e2c93
MappingWindow: don't store devq separately from controller default device
2017-11-19 12:46:39 -08:00
9551fe1c73
MappingWindow: m_controller is never nullptr
...
Since GCPadWiiUConfigDialog was made its own class, m_controller will
never be nullptr.
2017-11-19 12:46:38 -08:00
1e24a5f309
Merge pull request #6167 from ligfx/encapsulatedefaultdevice
...
EmulatedController: encapsulate default device behind getters/setters
2017-11-11 17:11:56 +01:00
a8b5eab4c4
Qt GCPadWiiU: standalone dialog, not subclass of MappingWidget
...
It uses none of the functionality of MappingWidget or the parent MappingWindow, and complicates the definition of the MappingWidget interface.
2017-11-05 08:04:16 -08:00
27e1577da9
Qt MappingWindow: move controller type into constructor
2017-11-05 08:04:16 -08:00
1b1dd1d749
EmulatedController: encapsulate default device behind getters/setters
2017-11-04 17:08:55 -07:00
806a8a7f32
MappingWindow: store profile filename in QComboBox userdata
2017-09-27 21:04:34 +02:00
5c29ea54c5
Merge pull request #5817 from JosJuice/qt-strings-match-wx
...
Make DolphinQt2 strings more like DolphinWX strings
2017-07-27 15:01:56 +08:00
80b938b403
DolphinQt2: Remove unimplemented prototypes
...
Also removes an unnecessary includes in related files
2017-07-26 16:26:55 -04:00
ce11b34e74
Make DolphinQt2 strings more like DolphinWX strings
...
Without this, we would be pushing a lot of extra strings onto
translators now that 55fb6ef
2017-07-26 08:04:10 +02:00
f106a9637d
Replace balanced Core::PauseAndLock calls with RunAsCPUThread
...
Core::PauseAndLock requires all calls to it to be balanced, like this:
const bool was_unpaused = Core::PauseAndLock(true);
// do stuff on the CPU thread
Core::PauseAndLock(false, was_unpaused);
Aside from being a bit cumbersome, it turns out all callers really
don't need to know about was_unpaused at all. They just need to do
something on the CPU thread safely, including locking/unlocking.
So this commit replaces Core::PauseAndLock with a function that
makes both the purpose and the scope of what is being run on the
CPU thread visually clear. This makes it harder to accidentally run
something on the wrong thread, or forget the second call to
PauseAndLock to unpause, or forget that it needs to be passed
was_unpaused at the end.
We also don't need comments to indicate code X is being run on the
CPU thread anymore, as the function name makes it obvious.
2017-07-21 16:45:59 +08:00
ed0ba7ef28
Qt: Don't show the Qt "What's this" button
2017-06-29 18:52:53 -06:00
5b6c8c3ad0
MappingButton: grab and release mouse and keyboard instead of calling parent SetBlockInputs
2017-06-15 16:15:07 -07:00
2188ac785a
Move MappingWindow::OnDefaultFieldsPressed() to correct file
2017-06-15 16:15:07 -07:00
e023cc124b
Qt/MappingWindow: Update layout to match WX
2017-06-13 22:42:53 -06:00
50c13c1902
Qt: Implement advanced mapping I/O windows
2017-06-13 17:16:41 +02:00
151ae38a56
Qt: Implement hotkeys (+ configuration)
2017-06-06 13:49:49 +02:00
548522877a
DolphinQt2: make Settings a singleton
...
With this, we can get signals when properties change.
2017-06-05 16:46:10 -07:00
d65006b91b
Qt: Fix games crashing on start
2017-05-23 22:12:01 +02:00
6370f094ba
Qt: Fix default device handling
2017-05-21 14:47:35 +02:00
33e111e92f
Qt: Implement button mapping dialogs
2017-05-20 17:53:17 +02:00
Michael M