* With multiple windows now a ComboBox popup has its own window (and
the size of the popup is not limited to the parent display anymore)
* Clicking in the parent ui::Window that is below the ComboBox listbox
in non-multiple windows mode doesn't start the resizing/moving loop
of the window (the click now is sent to the listbox correctly)
* Limit the position to the workarea (in multiple-windows) and to the
display (in non-multiple windows)
Before this fix if an image were allocated in the clipboard, then you
copied a Cel and wanted to paste it to other Cel, the previous image
were pasted in the canvas instead the last Cel copied in the timeline.
How to reproduce the bug:
- Make a sprite.
- Draw something on the canvas.
- Select a drawn region and copy the selection (the image is now in
the clipboard).
- Add a frame in the time line.
- Copy the Cel of frame 1.
- Select the empty Cel of the frame 2.
- Paste: you'll see the image selected in step 3 was pasted on the
canvas instead the last Cel copied on the timeline.
We've changed a restriction for tilesets: grid's in doc::Tileset must
have origin=(0,0); and the origin of a doc::Grid only makes sense for
the sprite grid (where the origin is set by the user) or for a tilemap
cel (where the origin is the cel origin).
Before this fix when we clicked on user data icon (to expand the window and show the user data), the expanded window were displayed incorrectly (some parts black, and other with an incorrent widget size).
Without this fix we would read old .aseprite files (saved with v1.2)
incorrectly: assigning user data that corresponded to other
objects (cels/slices/etc.) to tags.
Co-authored-by: David Capello <david@igarastudio.com>
As we wanted the current cel as the first cel to transform (to avoid
re-transforming it with inner cmds when we drop pixels), if this cel
was a linked from other one it will not be removed from the
getEditableCels() list, so two linked cels would appear two times in
the list. Now we remove the current cel correctly when it's a linked
cel after re-adding it.
Reported here: https://community.aseprite.org/t/8618
When we clicked the current cel/frame/layer on MovingPixelsState in
the Timeline, we weren't dropping the pixels, so the range was
different in the Timeline UI, but we were using the old site range
which was different (bigger) than the Timeline range.
Fixes several bugs: https://community.aseprite.org/t/8618
When eyedropper was used to pick tiles from a composed image having an
image layer and a tilemap layer without cels, it tried to pick tiles
from the image layer.
