mirror of
https://github.com/dolphin-emu/dolphin
synced 2024-11-24 14:24:11 -05:00
4d34f86121
Will manually controlling both an accelerometer and a gyroscope at the same time be reasonable to do? No idea. Was this easy to implement thanks to the input override system? Yes. Fixes https://bugs.dolphin-emu.org/issues/12443.
59 lines
1.8 KiB
C++
59 lines
1.8 KiB
C++
// Copyright 2023 Dolphin Emulator Project
|
|
// SPDX-License-Identifier: GPL-2.0-or-later
|
|
|
|
#include "DolphinQt/TAS/TASControlState.h"
|
|
|
|
#include <atomic>
|
|
|
|
#include "Common/CommonTypes.h"
|
|
|
|
int TASControlState::GetValue() const
|
|
{
|
|
const State ui_thread_state = m_ui_thread_state.load(std::memory_order_relaxed);
|
|
const State cpu_thread_state = m_cpu_thread_state.load(std::memory_order_relaxed);
|
|
|
|
return (ui_thread_state.version != cpu_thread_state.version ? cpu_thread_state : ui_thread_state)
|
|
.value;
|
|
}
|
|
|
|
bool TASControlState::OnControllerValueChanged(int new_value)
|
|
{
|
|
const State cpu_thread_state = m_cpu_thread_state.load(std::memory_order_relaxed);
|
|
|
|
if (cpu_thread_state.value == new_value)
|
|
{
|
|
// The CPU thread state is already up to date with the controller. No need to do anything
|
|
return false;
|
|
}
|
|
|
|
const State new_state{static_cast<int>(cpu_thread_state.version + 1), new_value};
|
|
m_cpu_thread_state.store(new_state, std::memory_order_relaxed);
|
|
|
|
return true;
|
|
}
|
|
|
|
void TASControlState::OnUIValueChanged(int new_value)
|
|
{
|
|
const State ui_thread_state = m_ui_thread_state.load(std::memory_order_relaxed);
|
|
|
|
const State new_state{ui_thread_state.version, new_value};
|
|
m_ui_thread_state.store(new_state, std::memory_order_relaxed);
|
|
}
|
|
|
|
int TASControlState::ApplyControllerValueChange()
|
|
{
|
|
const State ui_thread_state = m_ui_thread_state.load(std::memory_order_relaxed);
|
|
const State cpu_thread_state = m_cpu_thread_state.load(std::memory_order_relaxed);
|
|
|
|
if (ui_thread_state.version == cpu_thread_state.version)
|
|
{
|
|
// The UI thread state is already up to date with the CPU thread. No need to do anything
|
|
return ui_thread_state.value;
|
|
}
|
|
else
|
|
{
|
|
m_ui_thread_state.store(cpu_thread_state, std::memory_order_relaxed);
|
|
return cpu_thread_state.value;
|
|
}
|
|
}
|