- 04 Mar, 2017 2 commits
-
-
Craig Watson authored
-
Craig Watson authored
We can (again) check for updates and, if an update is available, send the user to the site to download them. The old format (a .json specifying a version number and download URL) was kept. The address for this file is now specified in the settings.
-
- 27 Feb, 2017 1 commit
-
-
Craig Watson authored
Fixes an issue where locked items could be moved if they were selected along with other items, and these items all moved by dragging the selection frame. This implementation prevents any movement of the selected items if at least one of them is locked. It also changes the colour of the selection frame, like a locked UBGraphicsDelegateFrame.
-
- 25 Feb, 2017 1 commit
-
-
Craig Watson authored
-
- 22 Feb, 2017 1 commit
-
-
Craig Watson authored
When drag-n-dropping a document to the trash, it would reappear in the "untitled documents" folder on the next restart. (This was introduced by bd3d8e95)
-
- 19 Feb, 2017 1 commit
-
-
Craig Watson authored
-
- 18 Feb, 2017 1 commit
-
-
Craig Watson authored
Added checks for the size of the interior, cut-out triangle to make sure everything is drawn correctly at small sizes; buttons are now also hidden if they overflow from the tool.
-
- 12 Feb, 2017 2 commits
-
-
Craig Watson authored
Also install the importer executable to OpenBoard root install folder
-
Craig Watson authored
This removes a few instances of deleting a scene twice, or accessing elements of a scene after they've been deleted. Previously, the application would crash upon exiting if the scene was empty but had been modified (e.g if an object was placed on the board then deleted, then the application closed)
-
- 11 Feb, 2017 1 commit
-
-
Craig Watson authored
Previously, only transforms were saved -- not positions (which are set if a group is moved by dragging it directly; if dragged by its frame, its transform is updated instead). Issue observed was that a group that had been moved would lose its new position when the document was saved then loaded. (All other transforms were kept, however). Now, when duplicating a group before saving a document, position is included in the group's transform.
-
- 04 Feb, 2017 1 commit
-
-
Craig Watson authored
-
- 01 Feb, 2017 1 commit
-
-
Craig Watson authored
-
- 28 Jan, 2017 2 commits
-
-
Craig Watson authored
This was observed in some cases on low-resolution screens, at least on Linux and Windows. The previously hardcoded value for the width of the text items' titlebar (consisting of the buttons for formatting text) was replaced by a method calculating its width (which varies based on screen resolution).
-
Craig Watson authored
-
- 25 Jan, 2017 4 commits
-
-
Craig Watson authored
... to the nearest 2 decimal places. This fixes a bug where upon loading a text item, it could be scaled by e.g 0.999999, which would eventually round down the point size by 1pt. Making the text item shrink by 1pt every time the document was opened.
-
Craig Watson authored
-
Craig Watson authored
Fixed issue that appeared with previous commit, where grouped strokes' positions were sometimes saved and loaded incorrectly. Strokes and their transforms should now be saved correctly whether they are grouped or not
-
Craig Watson authored
(Much simpler and cleaner solution than previous commit)
-
- 22 Jan, 2017 1 commit
-
-
Craig Watson authored
This reverts commit d7b73a16.
-
- 16 Jan, 2017 1 commit
-
-
EmPeWe authored
Credit: EmPeWe
-
- 15 Jan, 2017 3 commits
-
-
Craig Watson authored
-
Craig Watson authored
Solves issue where items (other than strokes) that had been grouped then moved (and/or rotated) lost their new position after saving and loading the document.
-
Craig Watson authored
-
- 14 Jan, 2017 3 commits
-
-
Craig Watson authored
- Selecting multiple media items then grouping them didn't behave as it should for other items => fixed by adding type tests - A group containing several media items wasn't saved to SVG with those media items as children, due to incorrect UUID copying in the mediaItems's deepCopy() methods
-
Craig Watson authored
-
Craig Watson authored
-
- 08 Jan, 2017 3 commits
-
-
Craig Watson authored
The same font, in the same point size, can be displayed differently depending on platform (this is a Qt limitation). This can lead to text items being the wrong size when importing a document created on a different computer. As a workaround, when saving a text item to SVG, the size of 1pt in pixels is calculated and saved. Upon loading, this value is calculated again and, if it is different from the saved value, the text item is scaled accordingly. Thus, any document created from this version onward will have correctly-scaled text boxes. If an old document (not containing a pixel-per-point attribute for text items) is loaded, the scene is marked as modified to make sure that all text items are then saved with the pixels-per-point value (even if the document is not edited). This allows old documents to be "fixed" by simply opening them once from a new version of OpenBoard. save text item font size in pixels, and scale it on load fixed loading of text item pixel height Save and load pixels-per-point rather than text pixel height Upon loading a text item from SVG, make sure that it will be saved with a pixel-per-point value
-
Craig Watson authored
This prevents crashes that may occur when deleting multiple pages from a document.
-
Craig Watson authored
-
- 27 Nov, 2016 1 commit
-
-
Craig Watson authored
-
- 26 Nov, 2016 1 commit
-
-
Craig Watson authored
-
- 15 Nov, 2016 1 commit
-
-
Craig Watson authored
-
- 14 Nov, 2016 1 commit
-
-
Craig Watson authored
-
- 13 Nov, 2016 1 commit
-
-
Craig Watson authored
This allows users to change the color of the background grid e.g if they are using a projector or other low-contrast display. The settings are in the `Board` category and are named `CrossColorDarkBackground` and `CrossColorLightBackground`. They take strings representing the color in any of the following formats: - #RGB (Hexadecimal digits) - #RRGGBB - #AARRGGBB - #RRRGGGBBB - #RRRRGGGGBBBB - Any SVG color keyword name (as defined by W3C)
-
- 06 Nov, 2016 6 commits
-
-
Craig Watson authored
This prevents a bug where a simplified stroke (containing only one polygon) was incorrectly saved as a polyline, which meant the stroke was lost when the document was loaded.
-
Craig Watson authored
Up until now, the fill rule of a polygon was always saved as even-odd, despite the fact that in most if not all cases, polygons are drawn with winding fill within OpenBoard. Saving is now fixed, but there is no way to know upon loading whether the polygon was correctly saved or whether; so for now, we just set the fill rule to Winding when loading a polygon.
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-
Craig Watson authored
-