mirror of
https://github.com/dolphin-emu/dolphin.git
synced 2024-09-21 20:01:40 +02:00
222fe58e25
Without this macro, if any signals or slots were attempted to be used, they wouldn't work; neither would various other features of the Qt meta-object system. This can also lead to weird behavior in other circumstances. Qt's documentation specifically states: "Therefore, we strongly recommend that all subclasses of QObject use the Q_OBJECT macro regardless of whether or not they actually use signals, slots, and properties." on its page for "The Meta-Object System", which can be seen here: https://doc.qt.io/qt-5/metaobjects.html Let's opt for "always do the right thing", and keep the code extensible for the future and not have random things blow up on us.
26 lines
500 B
C++
26 lines
500 B
C++
// Copyright 2017 Dolphin Emulator Project
|
|
// Licensed under GPLv2+
|
|
// Refer to the license.txt file included.
|
|
|
|
#pragma once
|
|
|
|
#include "DolphinQt2/Config/Mapping/MappingWidget.h"
|
|
|
|
class QHBoxLayout;
|
|
|
|
class HotkeyStates final : public MappingWidget
|
|
{
|
|
Q_OBJECT
|
|
public:
|
|
explicit HotkeyStates(MappingWindow* window);
|
|
|
|
InputConfig* GetConfig() override;
|
|
|
|
private:
|
|
void LoadSettings() override;
|
|
void SaveSettings() override;
|
|
void CreateMainLayout();
|
|
|
|
// Main
|
|
QHBoxLayout* m_main_layout;
|
|
};
|