Locking to 0-degrees when mouse is within a UI-button-sized
square centered around the stamp's center (h/t Pere for the idea).
Change mouse pointer to 'hand' when in the center (so at the start
of the rotation step), and to the 'circle arrow' rotation symbol
when actually rotating.
WIP (disabled for now) Drawing a XOR'd line out of the stamp's
center to the mouse, to show the angle you're rotating at.
(Needs more work to avoid leaving residuals on the screen.)
Rotation off of zero (0) degrees only occurs when dragging outside
the bounding box (rectangle around the width/height) of the stamp.
No longer warping mouse to the right of the stamp, to cause it to
default to zero degrees. (The mouse being at the center of the
stamp now causes this, per the above change.)
Motivation - Placing stamps on mobile (touchscreen) was difficult
and non-intuitive. Now, you can at least double-tap the same
spot on the screen to position, and then place (without rotation)
the stamp. It's still not perfect, and I think a UI option to
enable/disable stamp rotation (leaving it off by default) is needed.
e.g. if the aspect ratio of the template/starter is wider than
that of the canvas, and "autoscale=vertical" (or "=both")
is specified, before it would chop the top and bottom of the
image off, displaying the vertical center of it on the canvas.
Now you can ask it to gravitate towards the top or bottom, if they
have content that's of higher significance than the opposite side.
h/t Pere & Albert for the suggestion.
TODO - Document, set some suitable defaults for images we ship.
Now possible to set scaling and smearing options for
each starter or template image. A ".dat" file can be
created which describes whether it's okay to scale and crop
the image's top/bottom and/or left/right, and if not both,
whether to smear the sides of the starter/template to the
edges of the canvas (the prior behavior, and the default),
or use a specific solid color background.
Once finished, will close
https://sourceforge.net/p/tuxpaint/feature-requests/190/
Still to do:
+ Document
+ Remove debugging printf()s (change to DEBUG_PRINTF()?)
+ Add files for starters & templates that ship with Tux Paint
+ Test!
When in the middle of adjusting a drawing with Zoom or Perspective,
you could change the color. However, the background would not
relfect this until you further adjusted the zoom/perspective.
Now, a color change causes the background to update immediately.
This involved updating the Tux Paint Magic API to send more
arguments to each Magic tool's "XYZ_set_color()" function,
which means a bump in the API version.
(Forthcoming, all other Magic tools will have their set_color()
functions updated.)
Text from unfinished "Label" tool input would appear after
creating a New image or Opening an existing one. Mended.
Closes https://sourceforge.net/p/tuxpaint/bugs/246/
Mostly by Pere.
If only one display is available, when running in windowed mode
and asking for Tux Paint to appear in a width and/or height larger
than the display's dimensions, Tux Paint will fall back to
the maximum(s) the display is capable of.
e.g., on my laptop with 1920x1080, running "tuxpaint --2048x2048"
will fall back to 1920x1080 (and display a warning to stdout).
However, if I have my external monitor (also 1920x1080) attached,
it will happily open a 2048x2048 window. Not perfect, but an
improvement.
Closes https://sourceforge.net/p/tuxpaint/feature-requests/113/
For example, when using a font like OpenDyslexia which has a very
large line spacing, the text gets shrunk since the overall bitmap
is too big for the space on the buttons (compared to the contents).
Cropping the whitespace will allow the text to remain larger.
WIP - The method of cropping isn't great. Text with descenders
appear higher than text without, causing terrible alignment.
So for now, the new `crop_surface()` code is not being used.
Also, replace some "#ifdef DEBUG printf(...) #endif" with
a simple "DEBUG_PRINTF(...)". And other minor tweaks.
Avoid reading outside of the bounds of the `touched[]` array,
to help prevent crashes.
h/t Miyagi Andel for reporting,
Shin-ichi TOYAMA for pinpointing the issue,
and Pere Pujal i Carabantes for providing a solution
Closes https://sourceforge.net/p/tuxpaint/bugs/269
These strings have been around a long time, and are only now
being utilized. Their purpose is for translators to provide
some characters which their language uses, so Tux Paint can
score fonts (and raise them to the top of the list in the
Text and Label tools) higher when they support those characters.
Many translators either left the strings as-is (e.g., "<9>spare-9b"),
or translated them literally (e.g., "<9>yedek-9b" & "<1>додаткова-1a"),
so removed those (replacing with `msgstr ""`).
