This reverts commit 87ddd51. We're trying to see if we can get Debian building and Windows running to work at the same time
Previously, you would need to restart Pinta after installing a custom brush add-in.
Every brush needs to implement this differently, so it doesn't make sense to have a default implementation.
In addition to the bug in the report, this also fixes bugs where the selection would "teleport" to the new location if you clicked somewhere else in the text.
The bounding rectangle returned by Pango is much larger than what we need, and the code previously tried to make some adjustments. However, that didn't work very well, especially with large font sizes. Now, we just set the height to be the # of lines times the cursor height, which works very well.
This will allow file format importers to properly create dialogs if needed.
There were a few issues when this effect was ported from Paint.NET: - The radius needs to be computed based on the total area being drawn to. - The center offset was computed incorectly. - The offset parameter needs to be Cairo.PointD so that it is an offset.
- The context, stroke colour, and image surface are now passed into the DoMouseMove method. This removes the dependency on the PaintBrushTool class and allows the code to move into Pinta.Core. - This should make writing addins with custom brushes a bit simpler, as classes can just inherit from BasePaintBrush.
- Allow formats to be write-only. This might be useful for some types of addins, such as an ascii art exporter. - Added some documentation for the constructor's parameters. - Removed the Name property, which did not serve any useful purpose.
These weren't actually being used anywhere.
This should be helpful for people building addins. - Disabled warning 1591, which resulted in thousands of warnings about every undocumented public member. - Cleaned up a bunch of out-of-date documentation that was caught by the compiler.
This makes the dialog more robust when using file format addins, and also makes it easier to develop file format addins in cases where the format doesn't provide an easy way to load a scaled version of the image.
…tbrush. Renamed the GetColorBgra and SetColorBgra to GetColorBgraUnchecked, etc, to indicate that no validation is performed on the canvas coordinates.
layer in the layers list widget. This solution fixes the original issue (bug #1175733), and I reverted the changes that caused a regression (bug #1176847).
invalidation rectangle when zoomed in. The original code did not take into account that one pixel in the image can correspond to multiple pixels on the canvas when zoomed in. This resulted in the invalidation rectangle being slightly too small. However, the invalidation rectangle is usually too large, so it was hard to notice this bug in most cases.
The Move Selected tool depends on having a set of selection polygons. The original code cleared out the selection polygons, but created a selection path. The Move Selected tool then cleared out the path (since there were no selection polygons), which caused the crop tool to attempt to crop a zero-sized rectangle.
This should be helpful to users writing file format add-ins.
…son-master Conflicts: Pinta.Core/Classes/BaseTool.cs
…d for tools that have icons with shape
[Fix for bug #1175733] Update layer preview after pasting.
The history item is now created a bit earlier on to ensure that text is finalized before the effect gets applied.
The largest leaks were in the Flood Tool and the Finish Pixels history item.
…erly. This was exposed in commit f18ef8d, which corrected the stroke extents rectangle. There were rounding issues when converting from double to int, and the bounding rect doesn't seem to account for antialiasing.
The parent window is now passed to the file exporter, which will also allow custom file format exporters from addins to properly create dialogs if needed.