dolphin/Source/Core/DolphinQt/Config/Graphics/GraphicsChoice.h

// Copyright 2017 Dolphin Emulator Project
// Licensed under GPLv2+
// Refer to the license.txt file included.

#pragma once

#include "DolphinQt/Config/ToolTipControls/ToolTipComboBox.h"

#include "Common/Config/Config.h"

class GraphicsChoice : public ToolTipComboBox
{
  Q_OBJECT
public:
  GraphicsChoice(const QStringList& options, const Config::Info<int>& setting);

private:
  void Update(int choice);

  Config::Info<int> m_setting;
};
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00			`// Copyright 2017 Dolphin Emulator Project`
			`// Licensed under GPLv2+`
			`// Refer to the license.txt file included.`

			`#pragma once`

DolphinQt: Add the ability to show a tooltip for custom graphics controls 2020-10-17 00:05:43 -05:00			`#include "DolphinQt/Config/ToolTipControls/ToolTipComboBox.h"`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00
Config: Add support for enums This makes it possible to use enums as the config type. Default values are now clearer and there's no need for casts when calling Config::Get/Set anymore. In order to add support for enums, the common code was updated to handle enums by using the underlying type when loading/saving settings. A copy constructor is also provided for conversions from `ConfigInfo<Enum>` to `ConfigInfo<underlying_type<Enum>>` so that enum settings can still easily work with code that doesn't care about the actual enum values (like Graphics{Choice,Radio} in DolphinQt2 which only treat the setting as an integer). 2018-05-11 22:38:44 +02:00			`#include "Common/Config/Config.h"`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00
DolphinQt: Add the ability to show a tooltip for custom graphics controls 2020-10-17 00:05:43 -05:00			`class GraphicsChoice : public ToolTipComboBox`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00			`{`
DolphinQt2: Add missing Q_OBJECT macro to all QObject-related classes missing it 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. 2018-05-13 16:16:20 -04:00			`Q_OBJECT`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00			`public:`
Remove redundant Config prefix from ConfigInfo/ConfigLocation Both structs are already in the Config namespace. 2020-05-02 14:39:40 +02:00			`GraphicsChoice(const QStringList& options, const Config::Info<int>& setting);`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00
			`private:`
			`void Update(int choice);`

Remove redundant Config prefix from ConfigInfo/ConfigLocation Both structs are already in the Config namespace. 2020-05-02 14:39:40 +02:00			`Config::Info<int> m_setting;`
Qt: Implement graphics window and controls 2017-06-16 01:42:12 +02:00			`};`