Prior to this fix, when the following conditions were met:
- On a tilemap layer
- Tilemap mode = OFF
- Tool = Pencil
- Tileset mode = Manual
- Modifying an existing tile with the "quick line"
(i.e. holding down the SHIFT key)
resulted in incorrect tool behavior.
Prior this fix when using large thumbnail sizes on the timeline with
smaller cel images, instead of enlarging the thumbnail image to fit
the full area available, it just adds transparent whitespace around
the thumbnail image.
Before this fix changing a color palette and then remapping it would not
invalidate a tileset's cache. Immediately saving to the .aseprite format
after this would use the stale cache data instead of the current sprite
data.
For the Qt "qaseprite" image plugin, we're using Aseprite as git
submodule so that we can link to its laf, dio and render libraries.
In this case, `CMAKE_BINARY_DIR` refers to the build directory of
qaseprite. We need to use `CMAKE_CURRENT_BINARY_DIR` instead, which
always refers to the right location for the generated `zconf.h`.
Prior to this fix, duplicate folders and files were displayed on
the Home tab. Additionally, paths were sometimes not well-formed and
included "/.." strings.
Regression introduced in #4389
See #4843
When this option is enabled, it requires a version of TinyEXIF newer
than 1.0.2 (which is the latest version that has been released),
specifically the change in cdcseacave/TinyEXIF@d75f772. The request to
release a new version of TinyEXIF is cdcseacave/TinyEXIF#18.
This file can be used with --ignore-revs-file param or
blame.ignoreRevsFile config to ignore global formatting changes which
don't help to use git-blame.
This reverts commit d38565f64e4c0304b8ea2ae060c9e1c11ba5a863.
It added blank lines between one line member function definitions
inside class bodies/header files, something which is undesirable.
With the current code it makes no difference, but it will force new
definitions to be in its own block, e.g. we cannot define two
functions without a blank line between then.
Allows to format the code in better ways adjusting the comments to fit
the column limit. In few cases the comment will require to be moved to
other place (e.g. at the top of a statement rather than to the side of
it).
With this we prefer to format a function declaration as:
int function(arg1,
arg2,
arg3);
Rather than:
int function(
arg1, arg2, arg3);
Cons: This makes the definition of NewParams structures a bit worse.
With this we prefer to format function calls as:
int value = function(arg1,
arg2,
arg3);
Or:
int value =
function(arg1, arg2, arg3);
Rather than:
int value = function(
arg1, arg2, arg3);
Making PenaltyBreakAssignment bigger creates better looking
const/variable declarations, where the following term to the
assignment operator is in the same line.
