Fix access conflicts in HyperX controllers where keepalive thread was directly accessing hardware
This commit is contained in:
parent
2d141be356
commit
d13d54fcfd
7 changed files with 7 additions and 7 deletions
|
|
@ -329,7 +329,7 @@ void RGBController_HyperXAlloyElite2::KeepaliveThreadFunction()
|
|||
{
|
||||
if((std::chrono::steady_clock::now() - last_update_time) > std::chrono::milliseconds(1000))
|
||||
{
|
||||
DeviceUpdateLEDs();
|
||||
UpdateLEDs();
|
||||
}
|
||||
}
|
||||
std::this_thread::sleep_for(50ms);
|
||||
|
|
|
|||
|
|
@ -299,7 +299,7 @@ void RGBController_HyperXAlloyOrigins::KeepaliveThread()
|
|||
{
|
||||
if((std::chrono::steady_clock::now() - last_update_time) > std::chrono::milliseconds(50))
|
||||
{
|
||||
DeviceUpdateLEDs();
|
||||
UpdateLEDs();
|
||||
}
|
||||
}
|
||||
std::this_thread::sleep_for(10ms);;
|
||||
|
|
|
|||
|
|
@ -275,7 +275,7 @@ void RGBController_HyperXAlloyOriginsCore::KeepaliveThread()
|
|||
{
|
||||
if((std::chrono::steady_clock::now() - last_update_time) > std::chrono::milliseconds(50))
|
||||
{
|
||||
DeviceUpdateLEDs();
|
||||
UpdateLEDs();
|
||||
}
|
||||
}
|
||||
std::this_thread::sleep_for(10ms);
|
||||
|
|
|
|||
|
|
@ -355,7 +355,7 @@ void RGBController_HyperXKeyboard::KeepaliveThreadFunction()
|
|||
{
|
||||
if((std::chrono::steady_clock::now() - last_update_time) > std::chrono::milliseconds(50))
|
||||
{
|
||||
DeviceUpdateLEDs();
|
||||
UpdateLEDs();
|
||||
}
|
||||
}
|
||||
std::this_thread::sleep_for(10ms);;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue