- 14 Mar, 2016 5 commits
-
-
Craig Watson authored
-
Craig Watson authored
The previous solution didn't really have any effect; only a handful of settings were in the mUserSettings or mAppSettings at the moment it was called. The better solution is to just call value() in the constructor of UBSetting, which means the setting is cached as soon as it is created.
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
- 11 Mar, 2016 4 commits
-
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
- 09 Mar, 2016 10 commits
-
-
Craig Watson authored
- Sort by Z before duplicating a selection (so that relative Z's are kept) - in UBZLayerController, iterate only through UBGraphicsScene's fast access items, not QGraphicsScene::items
-
Craig Watson authored
-
Craig Watson authored
- Defined constants in UBSettings for highlighter preview circle colors - Switch between light and dark colors when changing backgrounds - For eraser: use color settings that were defined in UBSettings (they were ignored since the preview circle was added)
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
When a video is first loaded (placed on the scene), we play/pause it to load the first frame; but this was also called when the video was manually stopped. To avoid this, a mStopped attribute was added to UBGraphicsMediaItem. It is set to true only when the video is stopped by the user.
-
Craig Watson authored
-
Craig Watson authored
-
- 08 Mar, 2016 5 commits
-
-
Craig Watson authored
(Solution from previous commit worked only on Linux)
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
Merging of the new settings and metadata saving feature into the main development branch
-
Craig Watson authored
The documents' metadata.rdf file is now persisted only when a scene in the document is also persisted; as well as when the document is modified (trashed / path changed) in the the Documents pane. Code was cleaned-up a bit too (added a forgotten return value, etc)
-
- 07 Mar, 2016 4 commits
-
-
Craig Watson authored
(Reading is still done synchronously, for now at least)
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
+ clean-up in a few places
-
- 04 Mar, 2016 4 commits
-
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
Some settings were changed between v1.02 and 1.10 (current), and some of these changes cause OpenBoard to crash at launch. This commit adds a function to check for these specific new settings, and wipe the old values if they are found. This avoids problems when the user upgrades from 1.02 without deleting their configuration file. (This is an alternative to having a post-install script, which would be ineffective in a multi-user configuration)
-
Craig Watson authored
UBSettings::value() now saves the requested value to the settings "queue" (hash table) for faster subsequent access
-
- 03 Mar, 2016 1 commit
-
-
Craig Watson authored
-
- 02 Mar, 2016 4 commits
-
-
Craig Watson authored
This should cut down on disk access. Instead of loading and saving settings directly through QSettings instances (which occasionally read and write to their associated file; but there is no way to control how often this happens), they are now added to a QHash for in-app access. Save() and load() functions were also added to enable manually saving the settings, and loading all settings from file, respectively.
-
Craig Watson authored
During trashing of multiple documents, a new document was selected every time that one was moved to the trash -- even if it was about to be trashed itself. This is no longer the case; the selectADocumentOnMultipleTrashing() method was added to select the first unselected document found (but this is currently not used, as it seems OK to just select no document when we have just deleted a whole selection)
-
Craig Watson authored
-
Craig Watson authored
-
- 01 Mar, 2016 3 commits
-
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
That function requires access to variables that are initialized in videoItem and audioItem constructors, so it can sometimes fail when called from the superclass's constructor. It might be an idea to avoid those calls altogether though
-