LoweBowe/MuseScore
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
MuseScore/mscore/preferences.h

409 lines
21 KiB
C
Raw Normal View History

Initial commit
2012-05-26 14:49:10 +02:00
//=============================================================================
// MusE Score
// Linux Music Score Editor
//
fix #116881: dynamic translation
2016-06-30 15:34:02 +02:00
// Copyright (C) 2002-2016 Werner Schweer and others
Initial commit
2012-05-26 14:49:10 +02:00
//
// This program is free software; you can redistribute it and/or modify
// it under the terms of the GNU General Public License version 2.
//
// This program is distributed in the hope that it will be useful,
// but WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
// GNU General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
//=============================================================================
#ifndef __PREFERENCES_H__
#define __PREFERENCES_H__
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
/*
* HOW TO ADD A NEW PREFERENCE
* - Add a new define to the list of defines below
* - Add the preference to the _allPreferences map in the init() function in preferences.cpp
* and specify the default value for this preference
* - That's it. The preference is stored and retrieved automatically and can be read
* using getString(), getInt(), etc., and changed using setPreference()
*/
Initial commit
2012-05-26 14:49:10 +02:00
#include "globals.h"
add namespace Ms
2013-05-13 18:49:17 +02:00
namespace Ms {
fix #99236 remove mscoreGlobalShare/sound from soundfont path Preferences::sfPath is renamed "mySoundfontsPath", which adheres to same naming scheme for myPluginsPath and myTemplatesPath, and now only stores the user-specified soundfont folders (no longer stores mscoreGlobalShare/sound). Any synthesizers loading soundfonts must make sure to look in mscoreGLobalShare/sound in addition to mySoundfontsPath. Removing mscoreGlobalShare/sound from the stored path fixes a bug with portable AppImages, which use a different temporary directory for mscoreGlobalShare on every execution.
2016-02-22 14:21:38 +01:00
extern QString mscoreGlobalShare;
turn enum SessionStart into enum class
2014-07-01 14:44:45 +02:00
enum class SessionStart : char {
EMPTY, LAST, NEW, SCORE
Initial commit
2012-05-26 14:49:10 +02:00
};
// midi remote control values:
enum {
RMIDI_REWIND,
RMIDI_TOGGLE_PLAY,
RMIDI_PLAY,
RMIDI_STOP,
RMIDI_NOTE1,
RMIDI_NOTE2,
RMIDI_NOTE4,
RMIDI_NOTE8,
RMIDI_NOTE16,
RMIDI_NOTE32,
RMIDI_NOTE64,
RMIDI_REST,
RMIDI_DOT,
RMIDI_DOTDOT,
RMIDI_TIE,
New feature: added redo in Midi Remote Control
2014-12-15 13:23:59 +01:00
RMIDI_UNDO,
Initial commit
2012-05-26 14:49:10 +02:00
RMIDI_NOTE_EDIT_MODE,
MidiRemote for Real-time Advance
2016-08-08 17:46:43 +02:00
RMIDI_REALTIME_ADVANCE,
Initial commit
2012-05-26 14:49:10 +02:00
MIDI_REMOTES
};
turn enum MuseScoreStyleType into enum class
2014-07-01 15:06:21 +02:00
enum class MuseScoreStyleType : char {
remove oxygen theme
2017-08-17 22:08:09 +02:00
DARK_FUSION = 0,
experiment with Fusion Theme to replace Oxygen
2016-09-29 22:27:31 +02:00
LIGHT_FUSION
Initial commit
2012-05-26 14:49:10 +02:00
};
// MusicXML export break values
turn enum MusicxmlExportBreaks into enum class
2014-07-01 16:25:24 +02:00
enum class MusicxmlExportBreaks : char {
ALL, MANUAL, NO
Initial commit
2012-05-26 14:49:10 +02:00
};
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
//
// Defines for all preferences
// Every preference should have a define to ease the usage of the preference
// Make sure the string key has a sensible grouping - use / for grouping
//
#define PREF_APP_AUTOSAVE_AUTOSAVETIME "application/autosave/autosaveTime"
#define PREF_APP_AUTOSAVE_USEAUTOSAVE "application/autosave/useAutosave"
Move two more prefs to new preferences model
2018-06-05 19:32:43 +02:00
#define PREF_APP_KEYBOARDLAYOUT "application/keyboardLayout"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// file path of instrument templates
#define PREF_APP_PATHS_INSTRUMENTLIST1 "application/paths/instrumentList1"
#define PREF_APP_PATHS_INSTRUMENTLIST2 "application/paths/instrumentList2"
#define PREF_APP_PATHS_MYIMAGES "application/paths/myImages"
#define PREF_APP_PATHS_MYPLUGINS "application/paths/myPlugins"
#define PREF_APP_PATHS_MYSCORES "application/paths/myScores"
#define PREF_APP_PATHS_MYSHORTCUTS "application/paths/myShortcuts"
#define PREF_APP_PATHS_MYSOUNDFONTS "application/paths/mySoundfonts"
#define PREF_APP_PATHS_MYSTYLES "application/paths/myStyles"
#define PREF_APP_PATHS_MYTEMPLATES "application/paths/myTemplates"
fix #273032: Provide an easy way to install soundfont, templates and instruments.xml Introduce extensions files aka .muxt. These files are archives with additional data to extend MuseScore with soundfonts, templates, custom workspaces, etc. Update qzip to fix bug with symlink. Add extensions management to resource manager.
2018-06-05 20:17:21 +02:00
#define PREF_APP_PATHS_MYEXTENSIONS "application/paths/myExtensions"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_APP_PLAYBACK_FOLLOWSONG "application/playback/followSong"
#define PREF_APP_PLAYBACK_PANPLAYBACK "application/playback/panPlayback"
#define PREF_APP_PLAYBACK_PLAYREPEATS "application/playback/playRepeats"
fix #276217 Support-MIDI-IN-while-playback-engaged Can now play in any part while playback is engaged. PianoTools reflects both the note the user is pressing and the playback notes at the same time. Loop range is no longer automatically set when Play is pressed. Turning off auto loop range selection on pressing play is now a configurable option. Restoring commented out debug line.
2018-09-20 18:56:10 +02:00
#define PREF_APP_PLAYBACK_LOOPTOSELECTIONONPLAY "application/playback/setLoopToSelectionOnPlay"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_APP_USESINGLEPALETTE "application/useSinglePalette"
fix #297287: scale palettes with monitor resolution +collect_artifacts MuseScore 2 used to scale the palettes according to screen resolution, so they were the same physical size on all systems. This was broken in MuseScore 3 development, so palettes are too small on high DPI systems and too large on low DPI systems. This fixes the issue by reinstating the code in palette.cpp that scales the grid and mag by the global guiScaling setting (same setting used to scale the score view itself). That only affects places int he code where the "old" palettes are still used - keysig and timedig dialogs, etc. Similar but much code accomploishes the same in palettemodel.cpp for the "new" palettes. In addition, because users may *prefer* larger or smaller palettes, I added an advanced preference to specify global palette scaling (applied on top of the automatic DPI scaling). This value is factored in to the main palette scaling.
2019-11-18 20:44:30 +01:00
#define PREF_APP_PALETTESCALE "application/paletteScale"
Move two more prefs to new preferences model
2018-06-05 19:32:43 +02:00
#define PREF_APP_STARTUP_FIRSTSTART "application/startup/firstStart"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_APP_STARTUP_SESSIONSTART "application/startup/sessionStart"
#define PREF_APP_STARTUP_STARTSCORE "application/startup/startScore"
#define PREF_APP_WORKSPACE "application/workspace"
fix #34321 add 'normalize' option to export preferences
2018-08-07 14:34:33 +02:00
#define PREF_EXPORT_AUDIO_NORMALIZE "export/audio/normalize"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_EXPORT_AUDIO_SAMPLERATE "export/audio/sampleRate"
#define PREF_EXPORT_MP3_BITRATE "export/mp3/bitRate"
#define PREF_EXPORT_MUSICXML_EXPORTLAYOUT "export/musicXML/exportLayout"
#define PREF_EXPORT_MUSICXML_EXPORTBREAKS "export/musicXML/exportBreaks"
#define PREF_EXPORT_PDF_DPI "export/pdf/dpi"
#define PREF_EXPORT_PNG_RESOLUTION "export/png/resolution"
#define PREF_EXPORT_PNG_USETRANSPARENCY "export/png/useTransparency"
#define PREF_IMPORT_GUITARPRO_CHARSET "import/guitarpro/charset"
#define PREF_IMPORT_MUSICXML_IMPORTBREAKS "import/musicXML/importBreaks"
#define PREF_IMPORT_MUSICXML_IMPORTLAYOUT "import/musicXML/importLayout"
#define PREF_IMPORT_OVERTURE_CHARSET "import/overture/charset"
#define PREF_IMPORT_STYLE_STYLEFILE "import/style/styleFile"
#define PREF_IO_ALSA_DEVICE "io/alsa/device"
#define PREF_IO_ALSA_FRAGMENTS "io/alsa/fragments"
#define PREF_IO_ALSA_PERIODSIZE "io/alsa/periodSize"
#define PREF_IO_ALSA_SAMPLERATE "io/alsa/sampleRate"
#define PREF_IO_ALSA_USEALSAAUDIO "io/alsa/useAlsaAudio"
#define PREF_IO_JACK_REMEMBERLASTCONNECTIONS "io/jack/rememberLastConnections"
#define PREF_IO_JACK_TIMEBASEMASTER "io/jack/timebaseMaster"
#define PREF_IO_JACK_USEJACKAUDIO "io/jack/useJackAudio"
#define PREF_IO_JACK_USEJACKMIDI "io/jack/useJackMIDI"
#define PREF_IO_JACK_USEJACKTRANSPORT "io/jack/useJackTransport"
#define PREF_IO_MIDI_ADVANCEONRELEASE "io/midi/advanceOnRelease"
#define PREF_IO_MIDI_ENABLEINPUT "io/midi/enableInput"
#define PREF_IO_MIDI_EXPANDREPEATS "io/midi/expandRepeats"
#define PREF_IO_MIDI_EXPORTRPNS "io/midi/exportRPNs"
#define PREF_IO_MIDI_REALTIMEDELAY "io/midi/realtimeDelay"
#define PREF_IO_MIDI_REMOTE "io/midi/remote"
#define PREF_IO_MIDI_SHORTESTNOTE "io/midi/shortestNote"
#define PREF_IO_MIDI_SHOWCONTROLSINMIXER "io/midi/showControlsInMixer"
#define PREF_IO_MIDI_USEREMOTECONTROL "io/midi/useRemoteControl"
#define PREF_IO_OSC_PORTNUMBER "io/osc/portNumber"
#define PREF_IO_OSC_USEREMOTECONTROL "io/osc/useRemoteControl"
#define PREF_IO_PORTAUDIO_DEVICE "io/portAudio/device"
#define PREF_IO_PORTAUDIO_USEPORTAUDIO "io/portAudio/usePortAudio"
#define PREF_IO_PORTMIDI_INPUTBUFFERCOUNT "io/portMidi/inputBufferCount"
#define PREF_IO_PORTMIDI_INPUTDEVICE "io/portMidi/inputDevice"
#define PREF_IO_PORTMIDI_OUTPUTBUFFERCOUNT "io/portMidi/outputBufferCount"
#define PREF_IO_PORTMIDI_OUTPUTDEVICE "io/portMidi/outputDevice"
#define PREF_IO_PORTMIDI_OUTPUTLATENCYMILLISECONDS "io/portMidi/outputLatencyMilliseconds"
#define PREF_IO_PULSEAUDIO_USEPULSEAUDIO "io/pulseAudio/usePulseAudio"
#define PREF_SCORE_CHORD_PLAYONADDNOTE "score/chord/playOnAddNote"
#define PREF_SCORE_MAGNIFICATION "score/magnification"
#define PREF_SCORE_NOTE_PLAYONCLICK "score/note/playOnClick"
#define PREF_SCORE_NOTE_DEFAULTPLAYDURATION "score/note/defaultPlayDuration"
#define PREF_SCORE_NOTE_WARNPITCHRANGE "score/note/warnPitchRange"
#define PREF_SCORE_STYLE_DEFAULTSTYLEFILE "score/style/defaultStyleFile"
Use new preference model for part style
2018-02-16 00:05:38 +01:00
#define PREF_SCORE_STYLE_PARTSTYLEFILE "score/style/partStyleFile"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_UI_CANVAS_BG_USECOLOR "ui/canvas/background/useColor"
#define PREF_UI_CANVAS_FG_USECOLOR "ui/canvas/foreground/useColor"
Update styling
2019-09-03 11:53:46 +02:00
#define PREF_UI_CANVAS_FG_USECOLOR_IN_PALETTES "ui/canvas/foreground/useColorInPalettes"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_UI_CANVAS_BG_COLOR "ui/canvas/background/color"
#define PREF_UI_CANVAS_FG_COLOR "ui/canvas/foreground/color"
#define PREF_UI_CANVAS_BG_WALLPAPER "ui/canvas/background/wallpaper"
#define PREF_UI_CANVAS_FG_WALLPAPER "ui/canvas/foreground/wallpaper"
#define PREF_UI_CANVAS_MISC_ANTIALIASEDDRAWING "ui/canvas/misc/antialiasedDrawing"
#define PREF_UI_CANVAS_MISC_SELECTIONPROXIMITY "ui/canvas/misc/selectionProximity"
#define PREF_UI_CANVAS_SCROLL_VERTICALORIENTATION "ui/canvas/scroll/verticalOrientation"
fix #8808: Add option to limit scroll area of the navigator and the score view
2018-04-26 15:31:53 +02:00
#define PREF_UI_CANVAS_SCROLL_LIMITSCROLLAREA "ui/canvas/scroll/limitScrollArea"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_UI_APP_STARTUP_CHECKUPDATE "ui/application/startup/checkUpdate"
fix #273032: provide easy way to destribute soundfonts, templates, etc. Continue implementing extensions. Add installed extensions version check and update on MuseScore sturtup, add the related setting in preferences.
2018-06-17 21:40:48 +02:00
#define PREF_UI_APP_STARTUP_CHECK_EXTENSIONS_UPDATE "ui/application/startup/checkExtensionsUpdate"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_UI_APP_STARTUP_SHOWNAVIGATOR "ui/application/startup/showNavigator"
#define PREF_UI_APP_STARTUP_SHOWPLAYPANEL "ui/application/startup/showPlayPanel"
#define PREF_UI_APP_STARTUP_SHOWSPLASHSCREEN "ui/application/startup/showSplashScreen"
#define PREF_UI_APP_STARTUP_SHOWSTARTCENTER "ui/application/startup/showStartCenter"
Create Tours See https://musescore.org/en/node/274365 for a guide and more explanation Blog Posts: Week 6: https://musescore.org/en/user/1190941/blog/2018/06/25/gsoc-2018-beginner-mode-and-tutorial-creation-week-6 Week 7: https://musescore.org/en/user/1190941/blog/2018/07/02/gsoc-2018-beginner-mode-and-tutorial-creation-week-7 Week 8: https://musescore.org/en/user/1190941/blog/2018/07/09/gsoc-2018-beginner-mode-and-tutorial-creation-week-8 Week 9: https://musescore.org/en/user/1190941/blog/2018/07/16/gsoc-2018-beginner-mode-and-tutorial-creation-week-9 Week 10: https://musescore.org/en/user/1190941/blog/2018/07/23/gsoc-2018-beginner-mode-and-tutorial-creation-week-10
2018-07-17 17:18:55 +02:00
#define PREF_UI_APP_STARTUP_SHOWTOURS "ui/application/startup/showTours"
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
#define PREF_UI_APP_GLOBALSTYLE "ui/application/globalStyle"
#define PREF_UI_APP_LANGUAGE "ui/application/language"
#define PREF_UI_APP_RASTER_HORIZONTAL "ui/application/raster/horizontal"
#define PREF_UI_APP_RASTER_VERTICAL "ui/application/raster/vertical"
#define PREF_UI_APP_SHOWSTATUSBAR "ui/application/showStatusBar"
#define PREF_UI_APP_USENATIVEDIALOGS "ui/application/useNativeDialogs"
#define PREF_UI_PIANO_HIGHLIGHTCOLOR "ui/piano/highlightColor"
#define PREF_UI_SCORE_NOTE_DROPCOLOR "ui/score/note/dropColor"
#define PREF_UI_SCORE_DEFAULTCOLOR "ui/score/defaultColor"
#define PREF_UI_SCORE_FRAMEMARGINCOLOR "ui/score/frameMarginColor"
#define PREF_UI_SCORE_LAYOUTBREAKCOLOR "ui/score/layoutBreakColor"
#define PREF_UI_SCORE_VOICE1_COLOR "ui/score/voice1/color"
#define PREF_UI_SCORE_VOICE2_COLOR "ui/score/voice2/color"
#define PREF_UI_SCORE_VOICE3_COLOR "ui/score/voice3/color"
#define PREF_UI_SCORE_VOICE4_COLOR "ui/score/voice4/color"
#define PREF_UI_THEME_ICONHEIGHT "ui/theme/iconHeight"
#define PREF_UI_THEME_ICONWIDTH "ui/theme/iconWidth"
Expand workspace functionality The workspace now can save the following: - Palettes - Toolbars - Menubar - GUI preferences - GUI components Also, Basic and Advanced workspaces are no longer hard coded. See the following blog posts for more info: Project Description: https://musescore.org/en/user/1190941/blog/2018/04/26/gsoc-2018-beginner-mode-and-tutorial-creation-project-description Week 1: https://musescore.org/en/user/1190941/blog/2018/05/20/gsoc-2018-beginner-mode-and-tutorial-creation-week-1 Week 2: https://musescore.org/en/user/1190941/blog/2018/05/28/gsoc-2018-beginner-mode-and-tutorial-creation-week-2 Week 3: https://musescore.org/en/user/1190941/blog/2018/06/04/gsoc-2018-beginner-mode-and-tutorial-creation-week-3 Week 4: https://musescore.org/en/user/1190941/blog/2018/06/12/gsoc-2018-beginner-mode-and-tutorial-creation-week-4 Week 5: https://musescore.org/en/user/1190941/blog/2018/06/17/gsoc-2018-beginner-mode-and-tutorial-creation-week-5
2018-06-18 21:20:00 +02:00
#define PREF_UI_THEME_FONTFAMILY "ui/theme/fontFamily"
#define PREF_UI_THEME_FONTSIZE "ui/theme/fontSize"
fix #273601: Updated UI for pianoroll editor. Updating main piano roll display to have 12 rows per octave. Updating piano keyboard to track main piano roll window. Moving PianoKeyboard to its own file. Better tracking of playhead during playback. Drawing beat lines within measure. Scrollbars now adjusted for stasis when zooming in the pianoview. Piano ruler now showing tick marks respecting zoom level. Fixing scroll issue during playback. Taking direct control of selection. PianoItem is no longer a Qt object. Preping for note group drag. Can now drag pitch changes. Adjusting viewport pos when staff set. Removing CMakeLists.txt Adding CMakeLists.txt back in. Cleaning things up for resubmission. Now displaying drumset names in PianoKeyboard when relevant. Updating tracking signal in Pianoroll Editor. Cleanup. Locator lines no longer Qt objects. Removing redundant note move on mouse up. Now adjusting final event for playback. Now showing note voice name. Using Tpc to use note name tha reflects accidentals. Better checking for Position when opening Pianoroll window. Adding note for ctrl-click on rest. Swithing velocity type will now also adjust to equivilent velocity value. Better checking for single note selection. Pianoroll window. Adding note for ctrl-click on rest. equivilent velocity value. Better checking for single note selection. Ctrl-click now adds note to selection. Note up/down now correct direction for drumroll Fixing calcuation for switching note velocity. Can now horiz resize piano keyboard. Setting up new PianoLevels control for setting note event values. Now drawing subbeat divisions. Can now cut notes. User can now select data type to display. Can now use mouse to adjust levels. Adding undo to note event changes. Now smoother transition between absolute and offset level values. Smoother update communication between controls. Adding labels to piano levels. Removing unneccary blocking of scene() in pianoview. Now handles adjusting level with 1px wide mouse sweep. mouse sweep. 'c8199ac5a'. fix #273601: Updated UI for pianoroll editor. Now handling setting null staff. Adding missing .h files to CMakeLists.txt Removing undo step to avoid selection problem. Adding tool tip display. Keyboard display now adjusting to reflect transposition of instrument. Now showing part name in Piano Roll editor. Moving color display options into preferences. Levels editor now using preferences too. Fixing incorrent note being highlighted in piano roll editor. Base color now used for coloring levels panel. Cleaning code Investigating cut/pasete actions. Adding popup menu. Encapsulating selection into a command. Creating minimal popup menu. Can now insert notes of arbitrary duraition to piano roll. Adding dark and light color schemes to piano roll editor. Can now set subbeats to non powers of 2. Fixing bad rebase. Holding shift will clamp values to mousedown position. Adding dropdown to modify which white lines are shown behind notes.
2018-10-21 10:27:23 +02:00
#define PREF_UI_PIANOROLL_DARK_SELECTION_BOX_COLOR "ui/pianoroll/dark/selectionBox/color"
#define PREF_UI_PIANOROLL_DARK_NOTE_UNSEL_COLOR "ui/pianoroll/dark/note/unselected/color"
#define PREF_UI_PIANOROLL_DARK_NOTE_SEL_COLOR "ui/pianoroll/dark/note/selected/color"
#define PREF_UI_PIANOROLL_DARK_BG_BASE_COLOR "ui/pianoroll/dark/background/base/color"
#define PREF_UI_PIANOROLL_DARK_BG_KEY_WHITE_COLOR "ui/pianoroll/dark/background/keys/white/color"
#define PREF_UI_PIANOROLL_DARK_BG_KEY_BLACK_COLOR "ui/pianoroll/dark/background/keys/black/color"
#define PREF_UI_PIANOROLL_DARK_BG_GRIDLINE_COLOR "ui/pianoroll/dark/background/gridLine/color"
#define PREF_UI_PIANOROLL_DARK_BG_TEXT_COLOR "ui/pianoroll/dark/background/text/color"
#define PREF_UI_PIANOROLL_LIGHT_SELECTION_BOX_COLOR "ui/pianoroll/light/selectionBox/color"
#define PREF_UI_PIANOROLL_LIGHT_NOTE_UNSEL_COLOR "ui/pianoroll/light/note/unselected/color"
#define PREF_UI_PIANOROLL_LIGHT_NOTE_SEL_COLOR "ui/pianoroll/light/note/selected/color"
#define PREF_UI_PIANOROLL_LIGHT_BG_BASE_COLOR "ui/pianoroll/light/background/base/color"
#define PREF_UI_PIANOROLL_LIGHT_BG_KEY_WHITE_COLOR "ui/pianoroll/light/background/keys/white/color"
#define PREF_UI_PIANOROLL_LIGHT_BG_KEY_BLACK_COLOR "ui/pianoroll/light/background/keys/black/color"
#define PREF_UI_PIANOROLL_LIGHT_BG_GRIDLINE_COLOR "ui/pianoroll/light/background/gridLine/color"
#define PREF_UI_PIANOROLL_LIGHT_BG_TEXT_COLOR "ui/pianoroll/light/background/text/color"
fix dark theme style move button highlight colors to advanced preferences align button colors with the new colors palette
2019-06-11 15:14:33 +02:00
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_DISABLED_DARK_ON "ui/button/highlight/color/disabled/dark/on"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_DISABLED_DARK_OFF "ui/button/highlight/color/disabled/dark/off"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_DISABLED_LIGHT_ON "ui/button/highlight/color/disabled/light/on"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_DISABLED_LIGHT_OFF "ui/button/highlight/color/disabled/light/off"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_ENABLED_DARK_ON "ui/button/highlight/color/enabled/dark/on"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_ENABLED_DARK_OFF "ui/button/highlight/color/enabled/dark/off"
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_ENABLED_LIGHT_ON "ui/button/highlight/color/enabled/light/on"
Concert Pitch - fix styling to highlight blue like icon when ON Changes provide opt-in styling for toolbar button text so that, like toolbar button icons, they change color as they change state. - Stylesheet changes to allow text on toolbar buttons to change color when pressed (and other cases, e.g. being disabled). QToolButtons with the property "iconic-text" set to true get this new behaviour. (Note: at present the color values are from the hard-coded color values in miconengine.cpp. rather than from a stylesheet / theme file.) - Applied the "iconic-text" property to the "Concert Pitch" button so its text now changes color in the same way as icon images do on other toolbar buttons. - Ensure the "Concert Pitch" button changes height in line with toolbar buttons that contain icons. This is done in a similar way - and at the same time - that the Zoom Options and View Mode dropdown heights are adjusted. It's required because the "Concert Pitch" button, like the Zoom Option and View Mode buttons, has no icon that would generate the height changes for the button.
2019-05-21 18:24:33 +02:00
#define PREF_UI_BUTTON_HIGHLIGHT_COLOR_ENABLED_LIGHT_OFF "ui/button/highlight/color/enabled/light/off"
fix dark theme style move button highlight colors to advanced preferences align button colors with the new colors palette
2019-06-11 15:14:33 +02:00
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
class PreferenceVisitor;
Initial commit
2012-05-26 14:49:10 +02:00
//---------------------------------------------------------
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// Preference
Initial commit
2012-05-26 14:49:10 +02:00
//---------------------------------------------------------
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
class Preference {
private:
QVariant _defaultValue = 0;
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
bool _showInAdvancedList = true;
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
protected:
QMetaType::Type _type = QMetaType::UnknownType;
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
Preference(QVariant defaultValue) : _defaultValue(defaultValue) {}
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
public:
Preference(QVariant defaultValue, QMetaType::Type type, bool showInAdvancedList = true);
virtual ~Preference() {}
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
QVariant defaultValue() const {return _defaultValue;}
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
bool showInAdvancedList() const {return _showInAdvancedList;}
QMetaType::Type type() {return _type;}
virtual void accept(QString key, PreferenceVisitor&) = 0;
};
class IntPreference : public Preference {
public:
IntPreference(int defaultValue, bool showInAdvancedList = true);
virtual void accept(QString key, PreferenceVisitor&);
};
class DoublePreference : public Preference {
public:
DoublePreference(double defaultValue, bool showInAdvancedList = true);
virtual void accept(QString key, PreferenceVisitor&);
};
class BoolPreference : public Preference {
public:
BoolPreference(bool defaultValue, bool showInAdvancedList = true);
virtual void accept(QString key, PreferenceVisitor&);
};
class StringPreference: public Preference {
public:
StringPreference(QString defaultValue, bool showInAdvancedList = true);
virtual void accept(QString key, PreferenceVisitor&);
};
class ColorPreference: public Preference {
public:
ColorPreference(QColor defaultValue, bool showInAdvancedList = true);
virtual void accept(QString key, PreferenceVisitor&);
};
// Support for EnumPreference is currently not fully implemented
class EnumPreference: public Preference {
public:
EnumPreference(QVariant defaultValue, bool showInAdvancedList = true);
virtual void accept(QString, PreferenceVisitor&);
Initial commit
2012-05-26 14:49:10 +02:00
};
//---------------------------------------------------------
// Preferences
//---------------------------------------------------------
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
class Preferences {
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
public:
typedef QHash<QString, Preference*> prefs_map_t;
private:
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// Map of all preferences and their default values
// A preference can not be read or set if it is not present in this map
// This map is not used for storing a preference it is only for default values
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
prefs_map_t _allPreferences;
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// used for storing preferences in memory when _storeInMemoryOnly is true
// and for storing temporary preferences
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
QHash<QString, QVariant> _inMemorySettings;
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
bool _storeInMemoryOnly = false;
bool _returnDefaultValues = false;
bool _initialized = false;
QSettings* _settings; // should not be used directly but through settings() accessor
QSettings* settings() const;
// the following functions must be used to access and change a preference
// instead of using QSettings directly
QVariant get(const QString key) const;
bool has(const QString key) const;
void set(const QString key, QVariant value, bool temporary = false);
void remove(const QString key);
QVariant preference(const QString key) const;
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
QMetaType::Type type(const QString key) const;
bool checkIfKeyExists(const QString key) const;
bool checkType(const QString key, QMetaType::Type t) const;
Initial commit
2012-05-26 14:49:10 +02:00
Expand workspace functionality The workspace now can save the following: - Palettes - Toolbars - Menubar - GUI preferences - GUI components Also, Basic and Advanced workspaces are no longer hard coded. See the following blog posts for more info: Project Description: https://musescore.org/en/user/1190941/blog/2018/04/26/gsoc-2018-beginner-mode-and-tutorial-creation-project-description Week 1: https://musescore.org/en/user/1190941/blog/2018/05/20/gsoc-2018-beginner-mode-and-tutorial-creation-week-1 Week 2: https://musescore.org/en/user/1190941/blog/2018/05/28/gsoc-2018-beginner-mode-and-tutorial-creation-week-2 Week 3: https://musescore.org/en/user/1190941/blog/2018/06/04/gsoc-2018-beginner-mode-and-tutorial-creation-week-3 Week 4: https://musescore.org/en/user/1190941/blog/2018/06/12/gsoc-2018-beginner-mode-and-tutorial-creation-week-4 Week 5: https://musescore.org/en/user/1190941/blog/2018/06/17/gsoc-2018-beginner-mode-and-tutorial-creation-week-5
2018-06-18 21:20:00 +02:00
// Used with workspace
store preferences in workspaces sorted
2019-02-17 18:01:49 +01:00
QMap<QString, QVariant> localPreferences;
QMap<QString, QVariant> getDefaultLocalPreferences();
Expand workspace functionality The workspace now can save the following: - Palettes - Toolbars - Menubar - GUI preferences - GUI components Also, Basic and Advanced workspaces are no longer hard coded. See the following blog posts for more info: Project Description: https://musescore.org/en/user/1190941/blog/2018/04/26/gsoc-2018-beginner-mode-and-tutorial-creation-project-description Week 1: https://musescore.org/en/user/1190941/blog/2018/05/20/gsoc-2018-beginner-mode-and-tutorial-creation-week-1 Week 2: https://musescore.org/en/user/1190941/blog/2018/05/28/gsoc-2018-beginner-mode-and-tutorial-creation-week-2 Week 3: https://musescore.org/en/user/1190941/blog/2018/06/04/gsoc-2018-beginner-mode-and-tutorial-creation-week-3 Week 4: https://musescore.org/en/user/1190941/blog/2018/06/12/gsoc-2018-beginner-mode-and-tutorial-creation-week-4 Week 5: https://musescore.org/en/user/1190941/blog/2018/06/17/gsoc-2018-beginner-mode-and-tutorial-creation-week-5
2018-06-18 21:20:00 +02:00
bool useLocalPrefs = false;
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
public:
Initial commit
2012-05-26 14:49:10 +02:00
Preferences();
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
~Preferences();
void init(bool storeInMemoryOnly = false);
void save();
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
// set to true to let getters return default values instead of values from QSettings
Save locale-dependent preferences on first start
2018-09-13 21:43:28 +02:00
void setReturnDefaultValuesMode(bool returnDefaultValues) {_returnDefaultValues = returnDefaultValues;}
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
const prefs_map_t& allPreferences() const {return _allPreferences;}
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// general getters
QVariant defaultValue(const QString key) const;
bool getBool(const QString key) const;
QColor getColor(const QString key) const;
QString getString(const QString key) const;
int getInt(const QString key) const;
double getDouble(const QString key) const;
// general setters
Save locale-dependent preferences on first start
2018-09-13 21:43:28 +02:00
void setToDefaultValue(const QString key);
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
void setPreference(const QString key, QVariant value);
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// A temporary preference is stored "in memory" only and not written to file.
// If there is both a "normal" preference and a temporary preference with the same
// key the temporary preference is used
void setTemporaryPreference(const QString key, QVariant value);
/*
* Some preferences like enums and structs/classes are not easily read using the general set/get methods
* and therefore require specific getters and/or setters
*/
SessionStart sessionStart() const;
MusicxmlExportBreaks musicxmlExportBreaks() const;
MuseScoreStyleType globalStyle() const;
bool isThemeDark() const;
template<typename T>
void setCustomPreference(const QString key, T t)
{
set(key, QVariant::fromValue<T>(t));
}
// The midiRemote preference requires special handling due to its complexity
MidiRemote midiRemote(int recordId) const;
void updateMidiRemote(int recordId, MidiRemoteType type, int data);
void clearMidiRemote(int recordId);
Expand workspace functionality The workspace now can save the following: - Palettes - Toolbars - Menubar - GUI preferences - GUI components Also, Basic and Advanced workspaces are no longer hard coded. See the following blog posts for more info: Project Description: https://musescore.org/en/user/1190941/blog/2018/04/26/gsoc-2018-beginner-mode-and-tutorial-creation-project-description Week 1: https://musescore.org/en/user/1190941/blog/2018/05/20/gsoc-2018-beginner-mode-and-tutorial-creation-week-1 Week 2: https://musescore.org/en/user/1190941/blog/2018/05/28/gsoc-2018-beginner-mode-and-tutorial-creation-week-2 Week 3: https://musescore.org/en/user/1190941/blog/2018/06/04/gsoc-2018-beginner-mode-and-tutorial-creation-week-3 Week 4: https://musescore.org/en/user/1190941/blog/2018/06/12/gsoc-2018-beginner-mode-and-tutorial-creation-week-4 Week 5: https://musescore.org/en/user/1190941/blog/2018/06/17/gsoc-2018-beginner-mode-and-tutorial-creation-week-5
2018-06-18 21:20:00 +02:00
store preferences in workspaces sorted
2019-02-17 18:01:49 +01:00
QMap<QString, QVariant> getLocalPreferences() { return localPreferences; }
Fix #278873: GUI preferences with custom workspace not saving/loading after change
2018-11-28 16:28:11 +01:00
void setLocalPreference(QString key, QVariant value);
Expand workspace functionality The workspace now can save the following: - Palettes - Toolbars - Menubar - GUI preferences - GUI components Also, Basic and Advanced workspaces are no longer hard coded. See the following blog posts for more info: Project Description: https://musescore.org/en/user/1190941/blog/2018/04/26/gsoc-2018-beginner-mode-and-tutorial-creation-project-description Week 1: https://musescore.org/en/user/1190941/blog/2018/05/20/gsoc-2018-beginner-mode-and-tutorial-creation-week-1 Week 2: https://musescore.org/en/user/1190941/blog/2018/05/28/gsoc-2018-beginner-mode-and-tutorial-creation-week-2 Week 3: https://musescore.org/en/user/1190941/blog/2018/06/04/gsoc-2018-beginner-mode-and-tutorial-creation-week-3 Week 4: https://musescore.org/en/user/1190941/blog/2018/06/12/gsoc-2018-beginner-mode-and-tutorial-creation-week-4 Week 5: https://musescore.org/en/user/1190941/blog/2018/06/17/gsoc-2018-beginner-mode-and-tutorial-creation-week-5
2018-06-18 21:20:00 +02:00
void setUseLocalPreferences(bool value) { useLocalPrefs = value; }
bool getUseLocalPreferences() { return useLocalPrefs; }
void updateLocalPreferences() { localPreferences = getDefaultLocalPreferences(); }
Initial commit
2012-05-26 14:49:10 +02:00
};
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
// singleton
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
extern Preferences preferences;
Initial commit
2012-05-26 14:49:10 +02:00
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
// Stream operators for enum classes
// enum classes don't play well with QSettings without custom serialization
template<typename T, typename std::enable_if<std::is_enum<T>::value>::type* = nullptr>
inline QDataStream &operator<<(QDataStream &out, const T &val)
{
return out << static_cast<int>(val);
}
Initial commit
2012-05-26 14:49:10 +02:00
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
template<typename T, typename std::enable_if<std::is_enum<T>::value>::type* = nullptr>
inline QDataStream &operator>>(QDataStream &in, T &val)
{
int tmp;
in >> tmp;
val = static_cast<T>(tmp);
return in;
}
Initial commit
2012-05-26 14:49:10 +02:00
Adds an advanced preferences tab to prefsdialog Adds logic and GUI to handle preferences without adding a separate widget to prefsdialog. Changes within the application because of a preferences change still needs to be handled separately in other parts of the code. When adding a preferences there is the option whether to have the preference in the advanced list or not. If not a separate widget must be added to prefsdialog. Note: Enums are currently not supported (as there are no enums in the advanced list as of now, but can be easily added.
2018-02-15 11:33:44 +01:00
class PreferenceVisitor {
public:
virtual void visit(QString key, IntPreference*) = 0;
virtual void visit(QString key, DoublePreference*) = 0;
virtual void visit(QString key, BoolPreference*) = 0;
virtual void visit(QString key, StringPreference*) = 0;
virtual void visit(QString key, ColorPreference*) = 0;
};
add namespace Ms
2013-05-13 18:49:17 +02:00
} // namespace Ms
Change to new preferences model The old Preferences struct holding all preferences are removed in favor of a new Preferences class which acts as a proxy for QSettings. The settings stored in QSettings are accessed directly through access methods like getBool(key), getInt(key), etc. and changed with setPreference(key, value). Since we are using QSettings directly the preferences are stored automatically without the need for a custom write() and read() method like before. The preferences.cpp/.h and prefdialog.cpp/h are refactored to have fewer responsibilities than before. The Preferences class are all about storing and retrieving preferences - it should not contain any code to handle any other aspect of MuseScore. Testing: The Preferences class can be used in tests. All preferences are initialized with default values in mtest. If a test requires that a preference has a specific value it can be changed using setPreference() for that single test. In the tests the preferences are stored in memory only. The Preference class is supposed to be used as a singleton. In preferences.h an 'extern Preferences preferences' is set and it is defined in preferences.cpp. All files which includes preferences.h have access to the 'preferences' singleton and should use this to get and set preferences.
2017-11-29 08:21:36 +01:00
Q_DECLARE_METATYPE(Ms::SessionStart);
Q_DECLARE_METATYPE(Ms::MusicxmlExportBreaks);
Q_DECLARE_METATYPE(Ms::MuseScoreStyleType);
Initial commit
2012-05-26 14:49:10 +02:00
#endif
Reference in a new issue Copy permalink